Website and application development time is reduced in the last couple of years.
Companies are using content management systems and ready-made MVC. This has reduced the development time but the application/website testing time is not reduced.
As a test engineer or tester, we need to test the application for at least following criteria
1. Compatibility Testing – Test the application with the different browser and Operating systems. This also needs to cover different screen resolutions and mobile devices.
2. Functional Testing – Verify the application for expected functionality and make sure it meets the customer expectations.
3. Business Logic Testing – Make sure that developed application follows the business rules and regulations.
To cover all the types of testing with limited timeframe we need to use more technical testing than the conventional testing.
This blog post will help you to take some small steps to reduce the overall testing timeframe without compromising the product quality.
1. Frontend V/S Backend:
Many test engineers spend a lot of time in testing browser OS compatibility for the backend or widely known as the application admin panel.
If backend users are limited then make sure to limit the compatibility testing for the application backend.
In many cases, developers use the CMS like WordPress, Drupal or Kentico. In this case, limit your testing to the business requirement for the backend.
2. Testing Flow:
Use cases –> Business Logic Testing –> Functional Testing
Consider using more use cases and fewer test cases. Ask business analyst about how the customer is going to use the application and based on the answers develop use cases.
Confirm the use-cases with business analyst and consider them as the baseline for the application testing.
Using the use cases will allow you to uncover the most obvious bugs that customer may encounter during the User Acceptance Testing (UAT).
Initiate Business Logic Testing (BLT) as soon as the use cases testing is completed. BLT will help you uncover most of the bug that may impact overall functionality of the application.
Use Functional Testing at the end of the cycle to validate the system for various functional flaws.
Using the functional testing at the end of the cycle will
a. Increase test execution speed: As you walk through the application two times you remember the flow and it will boost the testing speed.
b. Focused Testing: As the testing, segments are focused on different segments each time the test effectiveness will improve and uncover critical bugs quickly.
3. Use Different Devices:
For each test execution use different devices and browser-OS combination. This way you can cover the compatibility testing along with all other testing cycles.
Keep a track of test execution cycle with excel for each use case execution with different combinations. (I will share sample excel file soon)
4. Use the same flow:
If you have a team of testers make sure each and everyone follow the same flow for the initial testing.
Using the same flow for testing will allow you to get quick results for the positive testing.
Some extra tips:
5. understand the application technically and update the testing scope based on the solution used for the development
6. Consider completing positive test cases before initiating the negative testing
7. If you are a non-technical tester, ask the developer about the application and research before starting a test.
Rapid application development requires Rapid testing strategy.
Rapid application testing can be achieved by actively understanding the technology and business requirements.
Feel free to ask me if you are facing any issues while implementing the Rapid Application Testing Strategy.
Please do let me know your comments for this post.