Game-Changing Workflow: Elevating Manual Testing with Level 1 Testing Protocol in Software Development

In my current company, Infolytx Bangladesh LTD. Nadim Saker bhaiya (Our Former Test Manager) introduces this amazing workflow called level 1 testing for manual testers, Where a manual tester assesses the feature on the dev's PC to ensure alignment with the requirements and design. After obtaining approval, the feature is published on the development and test instances for thorough testing.

This technique can be seamlessly integrated into agile methodologies like Kanban. let's break it down step by step:

1. A QA will aid in the task breakdown with his product knowledge and define the acceptance criteria
2. After finalizing the acceptance criteria for the feature a QA/Tester will write the acceptance test cases for that feature
3. When an assigned developer implements the feature, the Developer will ask to check if everything is implemented correctly in his work environment.
4. A QA/Tester will promptly assess the feature build within their work environment to verify the accurate implementation of the designed feature and its intended functionality.
5. QA/Tester will check the feature against the acceptance criteria that they have already written
6. QA/Tester will not be prompted to check the feature in a non-functional way and will not check other criteria for the testing
7. QA/Tester will have to address any misalignments of the requirements and design to the developer verbally (QA/Tester should not log any bugs in that state)
8. The developer will check the suggestions and will reconfirm with the QA/Tester or with the PM if necessary or if there is something that needs clarification
9. The developer will fix the issues and will again check with the QA
10. After QA give a green signal to the feature it will get pushed to the DEV and test instance
11. QA/Tester will finish their other activities when it gets published e.g. Automation, Exploratory testing, Other non-functional testing, Boundary value analysis (functional testing) etc.

Advantages of this technique

In an agile process, it is common to changes in the requirements during the implementation of the features, So developing a feature back and forth and deploying constantly on the instance can overwhelm the feature implementation, This technique will help to increase the workflow in agile methodologies as the developer and tester communication will be more precise and the team-building efforts will be increased.

Another perspective it will reduce confusion and differences in the product understanding. It will align the team members' perspectives in the same line. Feature building will be faster than before.

In an agile process, as the requirements changes are sudden and based on the product owners, business analyst needs all the team members will be aligned with the product needs and requirements.

After developing the feature unnecessary back and forth for the requirements will be eliminated.

Testers have to work less as they don't have to enlist every other requirement missing in the product for better visibility.

Tester can focus more on the other functional testing and non-functional testing.

Disadvantages of this workflow

QA/Tester must be 100% clear of the product needs and have to track all the requirements changing in the current product.

QA/Tester must not confuse any feature and have to double-check everything to confirm that there are no confirmation biases or that the requirements are defined correctly.

In the conclusion, this technique offers more advantages than the disadvantages of the product. Hence it could be your game-changing workflow in your company in an agile process.