A best practice is a way of doing things which leads to good and expected results when it is applied properly. Testing is a most important phases in software development life cycle. It is the only way to understand if the project is on way to be successful or it is going to be a failure.
Software Testing Best Practices:
Some of the testing best practices include:-
1.Test Case Creation
Once requirements have been created and approved, while coding is in process, its time to create test cases. The idea is to have a complete list of test cases completed before coding is complete, that way you do not waste time during the QA process.
Use the Test Type field (choice list) to identify the type of test:
4) Smoke Test
Test cases can be written in Excel Sheet, Word or Notepad. But, mostly testers prefer Excel to write manual test-cases for the application. Also, for writing test cases one must follow proper format.
2.Release Preparation / Regression Test Cases
Each new release has the potential to break existing features of your software. It is a great idea to have a list of regression test cases that are run to ensure that all the existing features work as originally designed.Prior to the testing process for the release, the existing test cases should be updated to ensure a high quality test process for the release.
Smoke tests are test cases which cover the main areas of the software being tested. These are about 20 -30 test cases. These are basic test cases which should work whenever new release is prepared. The smoke test should pass in order to proceed with deep testing. So in case the smoke tests fail the QA team returns the build to the development team.
4.Positive Testing and Negative Testing
Positive Testing is type of testing in which the testing is done to check the software is meeting the requirements through positive scenarios. The test cases are created based on the requirements given.
Negative Testing is performed to check the software for negative scenarios, to break the code. The tester puts error values in the application to be tested. Some of the negatives inputs include. Putting in wrong date formats, putting decimals, colons in number formats,etc.
It is a good idea to have some performance test cases designed for each release to ensure that each release maintains adequate performance. How the system responds to different type’s volume of load is check under performance testing.
Performance testing is divided into 2 parts:
1) Performance testing before the release of product and after the release of the product: In this case we can determine the release has been faster or slower.
2) The tester must reboot its machine and clear the cache before starting the performance testing.
6.User Acceptance Testing
When the application is handed over to the client, entire documentation should be made explaining the method of installation, any open defects, various roles etc.
7. Test Case Review
The test cases which are prepared will be reviewed by QA Manager. And, once QA Manager verifies and then if there will be some changes then QA Manager will suggest it to the respective person. And, once QA Manager feels that its perfect then and only then testing will be started.