Forum Discussion
In my daily software testing life cycle, I am using below approach before I start testing any AUT:-
- Gathering the requirement to test any modeules.
- Breaking the application under test into smaller modules.
- Writing the testcases.
- Making the testcases available before the developer starts coding.
- Grouping the testcases for regression testing.
- Maximizing the test coverage.
- Conversation with the developers.
- Don't let the developers to test their own code. unless, it is unit testing.
- Use the bug reporting tool sich as Rally, JIRA, HP-ALM
- Write clear, descriptive and unambigous bug report.
Basically, I change the testing process everyday based on the testing requirements.
And when it comes to measurement of testing process. We and the team use SalesForce for this purpose. It allows you to build personal dashboard for a business as a whole or every single employee in your business.
If you want to make sure that every team members stay focussed on the most important business metrics, there is no better solution than salesforce.
- avidCoder6 years agoSuper Contributor
nmrao I mean to say here is, the developers can test their own code using UNIT testing. Whatever they do. After that all the other types of testing should be done by testers only.
And, I have changed the sentence.
- avidCoder6 years agoSuper Contributor
And also, Developers normally work with the developer mindset of "how to make this work?". A good tester is thinking about "how to break this?" - a very different mindset. Unit testing and TDD does teach developers to change hats to some extent. Moreover, there can be a possibility of misunderstanding requirements. Therefore final acceptance tests should be conducted by someone as close to the client as possible.
Related Content
- 11 years ago
- 6 years ago
- 10 years ago
Recent Discussions
- 22 days ago