Tricks To Boost The QA Process In An Origination.

Tricks To Boost The QA Process In An Origination. To Achieve The 99% Bug-Free Software.  

As a QA, I know it’s not easy to achieve a 99% bug-free application/software. As it’s not only a QA job to achieve a bug-free application but its everyone’s responsibility who involve directly or indirectly to the application development.

To get a 99.99% bug-free application/software you need to build a strong QA Team and QA process in an origination. (I’m saying 99.99% it’s because considering the 0.1% unexpected bugs 😊).

For keeping the minimal Defect leakage ration I used to follow certain steps (listed below) while working on any Testing Projects no matter whether it belongs to Agile or Waterfall methodology.

I’m Pournima Tele with 9+ years of QA experience, currently working with IVL(Infovision Labs ltd.)@ Pune.

Work Closely With Business Analyses & Solution designers:

Getting involved in requirement gathering activity, calls and meeting with BA’s and stakeholders from the binging of the SDLC requirement gathering phase. This will help QA’s to understand the requirement form the end user point of view, as well as the QA’s, will define the testing scope and identify the application dependency in the earlier phase which will help BA’s and Development team to progress their work smoothly.

Key benefits to the project and client/customer:

Errors cost less when detected at an early stage. Remove blockers at an early stage.

Documentation Review:

Review the requirement documents thoroughly to understand the functionality from a business point of view as well as from the development point of view. In this step, you will identify the bugs/gaps in the actual requirement and the development part as in this step you will review the documents such as, BRS, SRS, FRS, SIG, HLD, etc. which should be in sync with each other.

Key benefits to the project and client/customer:

Improved documentation means a higher quality project for lower labor input and more accurate estimates.

Test Plan Or Test Strategy:

In this step, you will identify the actual testing scope and the testing platform which will help you to give an appropriate testing estimate.

Make sure that your Test Plan Or Test Strategy document should contain the in scope(features to be tested) High-level test scenarios(including positive and negative test scenarios), testing dependence, Risk & Assumptions, entry-exit criteria, testing platform(SIT, Performance, Functional, non-functional testing etc.), testing approaches(ETL, Manual, Automation testing etc.) if ETL and automation is applicable then tools which you are using for testing list it down., out of scope test scenarios(features not to be tested), Resources/roles & responsibilities, Major Deliverables( Test Plan, Test cases, bugs report, Testing signoff report), list of tools if any, Approvals(the document reviewed and approved by.. BA, Test Manager, etc. if applicable).

Key benefits to the project and client:

It will help to frame the sprint/ testing scope for the specific requirement. It also helps management to identify the resource utilization for the specific release.

Test Plan Document Handover To Testing Team:

In this step, the QA Lead/Test Manager will give a KT section on the created Test Plan/Test Strategy document. In this meeting only the QA team(the testing team who is going to write a test case and execute it will involve).

Key benefits to the project and client/customer:

The Test Plan/Test Strategy document will help testers to know the testing scope, risk & Assumptions, dependence, tools, etc. so that the test planning and execution will run smoothly.

Test Case Review Meeting With BA’s And Business People:

This is a platform where QA, BA, and Stockholder(it would be good if you involve dev team lead in some organization the call system designer(Dav team lead))in this meeting where everyone will get a chance to discuss the current Deliverables. It is an important step in any QA process as it will give an overview of the understanding of the requirement to QA/QA Team as well as in this meeting the testing scope will get finalized and approved by the BA and stakeholders.

Key benefits to the project and client/customer:

It will help all team members, to get the clarity on the Deliverables, the expectation for the Stockholder and BA & SD. Identify the missing test scenarios in an earlier stage. Developers will come to know about the components which might get impacted and changed by the current requirement.

Test Execution:

In this step, you will actually execute the test case which is return by you/team.(I’m not writing much about the test execution as it depends on the application platform and method of testing within the project.)

Key benefits to the project and client/customer:

At the earlier stage testing team are aware of the prerequisite, dependence and the scope of testing hence they will not get blocker at this stage. Apart from the bugs 😊

Show and Tell with BA’s:

This step is to call the internal show and tell section. It is very helpful to have an internal show and tell with BA before going to represent it to the business people. In his meeting Testing team or QA lead/Test manager will give the actual application demo to BA where he/she will explain the functionality developed and tested by them as per the requirement.

Key benefits to the project and client/customer:

Scheduling this meeting will help the team(QA and Dev team) to understand the product is developed as per the business requirement and if anything is missed in development that can get addressed and management will take a call to align it with the upcoming release.

Show And Tell With BA’s And Business People:

This step is to call the external show and tell meeting it will be the last release meeting as in this meeting you are going to demonstrate the required flow to the end users i.e. Business people. There is a possibility to have review comments from stakeholders that will get banded into the product backblock list.

Key benefits to the project and client/customer:

Scheduling this meeting will help everyone involved in this requirement to get a clear picture of the application is matching with the actual requirement. If there is some additional functionality is required by the end user and which is not documented in this meeting in terms of review comment it will get the document. Also, it gives a platform to add, remove or change the application behavior in terms of user experience. (Note: This will get as a change request if the changes are big to implement).

Testing Sign-off:

This will be the last step in the QA process. Where you will mention the testing coverage, conditional sign off if any, testing evidence, bug list, etc. will include.

Key benefits to the project and client/customer:

For tracking or auditing purpose this document/email can be referred by management.

In each step, you can find a bug, gap or dependence which helps you to address risk and blocker before the live release, here you are reducing unexpected live bugs.