Scribd
Upload
12 views5 pages

Test Strategy

This document outlines the test strategy for the Chummy Funding application, detailing objectives, scope, and testing approaches to ensure quality. It includes in-scope testing types such as functional, performance, and security testing, while outlining the test environment and defect management processes. Additionally, it highlights the importance of test metrics, risks, and the tools used for effective test execution and management.

Uploaded by

srikanth121
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
12 views5 pages

Test Strategy

This document outlines the test strategy for the Chummy Funding application, detailing objectives, scope, and testing approaches to ensure quality. It includes in-scope testing types such as functional, performance, and security testing, while outlining the test environment and defect management processes. Additionally, it highlights the importance of test metrics, risks, and the tools used for effective test execution and management.

Uploaded by

srikanth121
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/ 5

PROARCH

TEST STRATEGY – CHUMMY FUNDING APP.


1. Introduction
This document outlines the test strategy for ensuring the quality of the
Chummy Funding application. It describes the testing approach, scope,
objectives, and resources required for successful test execution.

2. Objectives
 Ensure that all features related to the Chummy Funding application are
implemented and working as per the requirements.
 Verify that the software meets business and functional requirements.
 Validate the performance, security, and usability of the system.
 Ensure functional testing of core modules, integration between
different modules, and performance of the application.
 Ensure testing coverage for mobile features, including the latest and
most used versions of Android and iOS.
 Conduct API versions testing, performance testing, backward
compatibility testing for iOS, Android, API versions (deprecated APIs)
and browser compatibility testing.
 Minimize risks associated with software deployment.

3. Scope
3.1 In-Scope
 Functional Testing
 Regression Testing
 Performance Testing
 Security Testing
 Usability Testing
 Compatibility Testing
 API Version Testing
 Backward Compatibility Testing (iOS, Android, API versions, Browser
Compatibility-Chrome and Safari)
PROARCH

3.2 Out of Scope


 Penetration Testing
 Globalization and Localization Testing.
 Cloud Testing

4. Testing Approach
 TDD (Test-Driven Development) Approach: Writing tests before
code implementation to ensure test coverage and design efficiency.
4.1 Test Levels
 Unit Testing: Performed by developers using automated test cases.
 Integration Testing: Ensures seamless interaction between modules.
 System Testing: Validates end-to-end business flows.
 Backward Compatibility Testing: Ensures newer versions of
software work with older versions.
 Exploratory Testing: Unscripted approach to software testing.
 User Acceptance Testing (UAT): Conducted by business users to
validate functionality.

4.2 Test Types


 Manual Testing: Exploratory, UI validation, and business logic testing.
 Automation Testing: Regression suite for faster test execution.
 Performance Testing: Load and stress testing to ensure scalability.
 Security Testing: Identifies vulnerabilities and ensures data
protection.
 API Version Testing: Ensures different API versions function correctly.
 Backward Compatibility Testing: Ensures older versions of mobile
apps and web applications remain functional.
PROARCH

5. Test Environment
 Environment setup is done using Azure webapp and CI/CD pipelines.
 Development Environment: Used for developing, testing, debugging
an application and used for unit testing.
 QA Environment: Dedicated to functional, system and regression
testing.
 Staging Environment: Mirrors production for UAT and final validation
before deployment.

6.Test Data Management


 Data Anonymization: Use anonymized production data where
applicable to ensure data privacy and compliance.
 Synthetic Data Generation: Generate synthetic test data to
simulate various edge cases and business scenarios.
 Data Versioning: Maintain different sets of test data versions for
regression and backward compatibility testing.
 Test Data Refresh: Periodically update and clean test data to ensure
relevance and accuracy.
 API and Database Testing: Validate test data integrity across APIs to
ensure consistency.

7. Defect Management
 Defects will be identified, logged, prioritized, and tracked using Azure
Tool.
 Severity:
o Measures the technical impact of a defect on the system's
functionality.
o Categorized as "Critical," "Major," "Minor," or "Low."

o Determined by the tester based on the defect's impact on user


experience.
 Priority:
o Indicates how urgently a defect should be fixed, considering
business needs and project timelines.
PROARCH

o Categorized as "High," "Medium," or "Low."

o Decided by the project manager or product owner in


consultation with stakeholders.
 Severity and priority will be assigned based on business impact.

8. Test Automation Strategy


 Identify stable and frequently executed test cases for automation.
 Use Ranorex/Selenium for scripting and execution for UI.
 Maintain a regression test suite to cover core functionalities.

9. Test Metrics & Reporting


 Test Execution Rate: Percentage of tests executed.
o Formula: (Number of Executed Test Cases / Total Time Spent
Testing) × 100%
o Target: Average of 100% should be achieved.

o Purpose: Monitor the pace of test execution, identify areas for


improvement in test case design or automation, and ensure
timely completion of testing activities within project deadlines.
o Tracking Progress: Compare execution rates across different
test cycles or projects to identify trends and areas for
improvement.
o Risk Management: Identify potential risks if the test execution
rate falls below expected levels.
 Defect Density: Number of defects found within a
component/module.
o Purpose: Identifies areas of the software that require more
testing and improvement by highlighting sections with a high
defect density.
o Interpretation:

 Lower defect density → Better code quality.


 Higher defect density → Potential issues and areas for
further investigation.
PROARCH

o Key Aspects:

 Prioritizing testing efforts.


 Evaluating testing effectiveness.
 Identifying root causes.
 Test Coverage: Percentage of requirements covered by test cases.
The average should be 100%.
 Defect Resolution Time: Average time to resolve defects.

10. Risks & Mitigation

Risks Mitigation

Unstable test environment. Regular monitoring and backup


environments
Delayed defect resolution. Frequent defect triage meetings

Device compatibility issues. Maintain a device lab with updated OS


versions

API versioning conflicts. Regular API compatibility testing

Test execution rate fails. Use Test Metrics.

11. Tools & Technologies


 Test Management: Microsoft Azure.
 Automation: Selenium
 Performance Testing: *still to decide.

You might also like