Question: I’m so confused. I was a Quality Tester at my last job, but here the employees seem to use the titles Quality Assurance, Quality Control and Testing interchangeably. I started out in a more traditional organization, but now I’m a tried and true agile believer. Since I have no job description, what are my responsibilities?
A.
The three concepts are often used interchangeably. Ask what it means in your new organization and accept that as your role in your workplace reality despite the real definition.
B.
Find the specific meanings for each term from a university professor in the town where you work. Use that information to correct the organization so that they use proper terminology.
C.
Once you learn your job description from Human Resources, create a new title for yourself so that others can understand what you do. Perhaps Defect Engineer would be apt.
D.
Since agile teams work without formal processes or documentation, there is no need to answer to a particular title. Everyone on the team is merely a team member.
Have you realized that your organization is not putting enough attention on requirements? Wondering what types of tools are out there and how much they cost? Do you even need a tool? And if so, what kind?
The waterfall methodology for projects is aptly named, because it is equally painful to try to go back to prior phases of a project once the effort has advanced to the next phase. This article will outline two reasons to avoid waterfall, and three ways to approach software projects that are more useful.
Being a strong tester means being critical and assertive. This ability is not easy to control and can lead to finding flaws in all sorts of everyday surroundings. How to communicate these errors and mistakes without being a first-class jerk is also difficult. Can you keep everyone's frown upside down?
In software development, testing is one of the most important functions. But too often, there is a fundamental problem: We aren’t always testing the right things. Where’s the quality? Testing is a relative exercise, not an absolute one.
This procedure describes the process of testing software code or products by the test team. It documents the procedure for the entire testing cycle: generating test plans, scheduling tests, conducting tests and reporting test results. This procedure applies to new development, as well as major and minor releases, including customized solutions delivered to customers.
Do you know how to thoroughly and efficiently test the software product you have so painstakingly built? Don't risk delivering a faulty software product due to insufficient or unfocused testing. Use this list to check whether you are testing smart--or just testing!
Defining and measuring software quality attributes is critical to the success of any distributed application, and performance is no exception. Distributed applications must demonstrate performance in order to assure immediacy. Use this project plan to stay on top of your Performance Testing.
