[go: up one dir, main page]
Scribd
Upload
41 views2 pages

Test Data Matrix

The document outlines the problematic areas in a product, specifically focusing on P1-card License Changes and P-1 Cards, with over 70% automation coverage. It details the automation framework used, which is based on Rest Assured with TestNG and Maven, and highlights that the automation percentage for the product is approximately 19%. Additionally, it describes the testing approach as a mix of manual and automated testing, each constituting about 50% of the testing efforts.

Uploaded by

vivek.ggs
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views2 pages

Test Data Matrix

The document outlines the problematic areas in a product, specifically focusing on P1-card License Changes and P-1 Cards, with over 70% automation coverage. It details the automation framework used, which is based on Rest Assured with TestNG and Maven, and highlights that the automation percentage for the product is approximately 19%. Additionally, it describes the testing approach as a mix of manual and automated testing, each constituting about 50% of the testing efforts.

Uploaded by

vivek.ggs
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

Problematic Areas in the product and % of Automation around


the problematic Areas: The areas in the product where we observe
lot of issues during ST and from Customers. And what is the
automation coverage around this. -

Problematic Areas- P1-card License Changes and P-1 Cards,

The percentage of Coverage around P-1 Card is more than 70%, few
more regression and edge/negative cases need to be added.

2. %age of automation: The percentage of automation for the product


and reference from where this automation percentage is calculated.

We have automated 30 test cases, covered around 23 APIs, we should


be having around 120 APIs, so calculation is 23/120 = ~19%

3. Automation framework: The details of the automation framework


used to automate the product-Automation Framework –

 Our Framework is Rest Assured (Java) based Backend Automation


Framework using TestNG for test Management, and Maven for
maintaining Dependency.
 We are using Extent Report for report configuration and
generation and GitHub Runner for running our scripts through
CI/CD pipeline.
 We have integrated our framework with Playwright to start
covering UI end to end Automation and Configured our tests to
run on both stage and prod.

4. Automation framework maintenance: How scalable is the


automation framework from the maintainability and adding new
automation perspective.

Automation framework is easy to maintain, and reusable written


using object-oriented java features and could be easily integrated
through UI Automation and different tools.

Test Data handled through JDBC connection and hardcoded values are
maintained in a separate file ,reusable methods, classes and utilities
written to maintain code.

5. How/where we are tracking the regression issues: The


mechanism used in your product to the regression testing and where
are we tracking these regression test cases and issues identified during
regression testing for every release.
We are maintaining regression test cases/Acceptance tests on
Confluence and Issues also in Confluence Page.

6. Manual or automation or both: How is your product tested. Through


manual testing or automation or both. If what is the percentage of
each category.

We are testing test cases both Manually and through Automation.

Manual execution-We are testing boundary/edge use cases and


Acceptance tests Manually. ~50%

And we test Happy path, regression, Negative use case through


Automation, started with P-1 Card automation and working on towards
complete Automation. -50%

You might also like