How To Set Up A Qa Process

16 Nov 2022

Welcome to function 2 of our serial on the Agile QA procedure. The get-go part of the serial gave an overview of and introduction to the stages of the Agile QA process. Office 2 of the series volition take you through the steps to follow to set up your own process from scratch.

Setting up an Agile QA process from scratch can be quite daunting. 1 must keep in mind that having a working QA process from a previous organisation does non hateful it would work or fit all scenarios. So, on that note, instead of providing a hard gear up of guidelines to follow, I am going to share the thought process to assistance you set upwardly your ain framework to fit an organization so you lot can striking the footing running:

1. Know your production

First and foremost, the QA must empathize what blazon of product the application under development is and its purpose. This is a adept fashion to first gathering high level information about the system's architecture and the different systems that could be involved. This allows the QA to anticipate what types of testing should exist carried out based on experience. For case, if the system under development is a retail web application, the first things that come to mind are UI testing, backend testing, cross-browser testing, performance testing etc.

2. Know the product's hurting points

Now that we know what the product is and its purpose, it is time to get an understanding of what the product pain points are. This is usually done by conducting interviews with the product possessor and business organisation analyst, and sometimes with product end users. The main goal of this stride is to empathise the functionality that is considered high take a chance and make certain these risks are catered for in the overall test strategy. Here are a few sample questions that can help affluent out product pain points:

• What are the most common bugs leaking into production?
• Which functionalities/ modules are considered unstable?
• Were there any security breaches earlier?
• Is the organization performant?

3. Know your product's audience

To create a cost-effective and value-driven QA framework, the QA should know who will be using the actual software product. Understanding the target audience will allow the QA to tailor the procedure effectually the users' needs. This will and then allow the QA to shift the testing focus to features that are considered loftier-value, and as a result, relieve pregnant time and money.

For case, the actual stop-users only use Google Chrome'due south latest version in their organisation to navigate the production website. This means:

• Cross-browser testing can be ignored in this scenario.
• Testing the production on the latest version is acme priority.
• Testing the production on the latest version -ane could exist considered.

4. Create the QA process document

While working in an Agile environment promotes edifice working software over creating comprehensive documentation, it doesn't necessarily hateful that we should skip the whole documentation procedure birthday. Substantially, the goal of the QA process certificate is to maintain QA activities in a structured manner and to serve every bit a guide for newly hired QAs.

 Generally, the QA process certificate should contain:

• Description of the QA steps detailing what, when, and how QA fits in every stage of the Agile development process e.m.

Agile Development Stage/ Scenario	High-level QA Steps
Once piece of work detail User Story/ Acceptance are written	QA needs to review the user story/ acceptance criteria for: – Completeness – Clarity – Redundancy – Consistency – Testability
When acceptance criteria has changed	Revisit examination cases and estimate testing attempt and additional regression tests if required.
When a bug is discovered	Record and triage issues with the project squad members. Track the problems progress – the end state should either be airtight or deferred depending on the bug severity and priority.
When a bug is fixed, or code update is deployed	Sympathise the alter and its impact with project squad members. Then plan manual and/ or automated regression tests, and execute those tests.
Testing is completed on a work particular	Communicate test results and observations with the project team members to get feedback.

• The exam strategy

Content	High-level Description
Testing objectives	Testing objectives are usually aligned with the project or concern goals e.one thousand., some projects focus on delivering high awarding stability while others focus on abiding commitment past ways of quick feedback and defect prevention rather than defect detection.
Life cycle of piece of work items	Define the "Definition of Prepare" and "Definition of Washed" criteria for various work items (Chore/ Bug).
Types of Testing	Details the What, Who, Where, When, and How for each testing type: – Unit Testing – Credence Testing – Regression Testing – Exploratory Testing – Performance Testing – Security Testing, etc.
Roles and Responsibilities	Defines the team member's role and responsibilities on each examination level.
Test Automation Strategy	Defines how automation frameworks will be utilised throughout testing. It includes planning which tests should be automated, target test environments, setting upwards test data, execution logs and reporting exam results.
Test Tools	Details the tools to be used for each test level e.m. Postman or SOAP UI for API testing, SQL Server Management Studio for database testing, JMeter for performance testing, etc.
Exam Environments	Details the environs for development, testing, and UAT.
Test and Defect Management Tools	Details the management tools to capture various testing metrics. These metrics will then be used to evaluate the effectiveness of the test strategy e.g. Azure DevOps, TestRail, JIRA, etc.

5. Implement the QA process and monitor the results

In one case the QA procedure is documented and communicated across the projection team, it's now time to implement the procedure and evaluate its effectiveness. The aim is to ensure that critical bugs are not released to production. Here are a few metrics that tin can be used to measure software quality in Agile:

• Number of bugs plant in testing
• Number of bugs found in production
• Test Effectiveness = IB/ (IB + EB)
  • Where:
    • IB = Internal bugs found in testing
    • EB = External bugs institute in production
• Test Coverage (% of code covered in automated testing)

By post-obit these steps, y'all can set an Agile QA process that works for your organisation and the specific product involved. Look out for the final function in the series roofing best practices for the Agile QA process.

By Alvin Maranan

Exam Engineer

Alvin has 10 years feel in transmission and automatic testing. Having ISTQB Advanced Level Test Analyst and Technical Exam Analyst certifications under his chugalug, he seeks to continuously improve both manual and automated testing practices and institute robust QA processes to ensure high quality outcomes.

How To Set Up A Qa Process,

Source: https://www.senseiprojectsolutions.com.au/5-steps-to-set-up-an-agile-qa-process-from-scratch/

Posted by: louviereharms1968.blogspot.com

Share this post