TestStrategies
docx
keyboard_arrow_up
School
Concordia University *
*We aren’t endorsed by this school
Course
2012
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
7
Uploaded by MinisterTree940
Test Strategy
Project Name:
SystemFusion
Prepared By:
Gaganjot Singh
Date
:
27-05-2023
Current Test /
Project Phase:
Testing Planning
1
Introduction to Project
Google’s self-driving car company, Waymo is being merged with best buy stores that is
resulting in 750 rebranded stores all around Canada. There is an expected 25% growth in
sales per year for the next 5 years. Currently, all stores manually enter their sales info in a file
and then send it to the head office in London, Ontario.
The goal of the project is to create a new data entry system that will be web-based. The users
will enter their data into this system and then the data will be sent to the new COBOL system
to create sales reports. There will be a database to store the data. Then Java and Python will
be used to analyze this data to help in making better future business decisions. All these
systems will have to be created in this project.
Technical context: There is a web-based system that will be developed in Java and javascript.
The data storing database will SQL based. The sales processing and report generation system
will be COBOL based. Business analysts will use Java and Python to analyze the data.
2
Test Methodologies
Web-based data entry system:
1.
Unit testing: This will be a white box testing methodology used to test the individual
elements of the data entry system to see if they work according to their specification and
are using correct internal logic.
2.
Integration testing: We will use both white and black box testing for this. We will if
different modules or interfaces of the data entry system are interacting with each other
correctly.
3.
System testing: This will be mostly black box testing to see if the whole system
assembles and provide correct data entered by the user to the next system.
4.
Acceptance testing: This tells us if the users at different stores will accept this system to
enter their daily sales data and if this will fulfill their needs.
COBOL System:
1.
Unit testing(white box): To check if all components are using the correct internal logic.
2.
Integration testing(white box and black box): To check if different components will
interact correctly to create the sales reports.
3.
System testing(black box): To check if sales processing and report generation is done
correctly by the system
Page 1 of 7
Test Strategy Template v 1.4 (2021)
Test Strategy
-
SystemFusion
SQL database:
1.
Unit testing(white box): To check all the elements of the database are storing information
correctly.
2.
Integration testing(white box and black box): To check if all data columns are providing
all the information needed.
3.
System testing(black box): To see if the system is successfully storing the necessary data
and providing it when necessary.
Overall System:
1.
System integration testing: To see if different subsystems interact successfully with each
other and use the correct logic internally and externally. The data entry system should
provide correct and all information to the COBOL system. The COBOL system is able to
store information in the database.
Also, the old data entry system should be able to work with the newer systems.
2.
System testing: Next, if the whole system is working according to the specifications of
the project. All subsystems are working harmoniously to create a bigger system.
3.
Acceptance testing: Finally, if the whole system fulfills the specifications of the project
and helps with future business needs of the organization.
3
Resource / Environment Dependencies
1.
Environments:
Development Tools and Environments: JDK so Java code can be executed,
JavaScript IDE like Visual Studio code.
Source Code Management: Git can be used for version control
Build Automation: To automate the build of the software, tools include Jenkins or
Ansible.
Collaboration Tools: Communication tools like Zoom, project management tools,
and repositories platform like Github.
Test Environment: A testing environment where we can create production
conditions.
Test Data: Test data sets covering various real world scenarios.
Test Automation Tools: Selenium and Junit for unit testing.
Integration Test Environment: A environment where integration testing can be
done.
Other Tools: Tools to get feedback from stakeholders and users.
2.
Configuration Management:
Page 2 of 7
Test Strategy Template v1.4 (2021)
Test Strategy
-
SystemFusion
Version Control System: Git can be used for version control and document
changes.
Configuration Management Tools: Ansible, Chef, or Puppet can be used to
manage and deploy configurations in different environments.
Build Management: Tools like Jenkins to automate the build and deployment
process.
3.
People Roles:
1.
Java Developers
2.
JavaScript Developers
3.
Database Developers
4.
UI/UX Designers
5.
Business Analysts
6.
End Users
7.
Testers
8.
Test Automation Engineers
9.
Performance Testers
4.
Project Constraints:
Time Constraint:
Proper timeline to put different checkpoints of the project.
Cost Constraint:
There should be a fixed budget for the project.
Technical Constraint:
Older data entry systems should integrate with newer
systems and Sales Processing Subsystem should integrate seamlessly with other
subsystems. The integration process should account for compatibility between
different technologies, databases, and programming languages used by the
systems.
4
Testing Objectives/Approach
Data Entry System:
Fundamental operation of the system will be tested to confirm that sales
data can be accurately entered and stored in the database. The scope also includes additional
situations including managing exceptions, checking data validation rules, and user interface
usability. To ensure that it interfaces properly with other systems and has accurate data
transmission.
COBOL System:
Modules will be validated throughout testing to guarantee accurate data
processing. To ensure correct data transfer, error management, and synchronization between
the Sales Processing Subsystem and other components, integration testing will be carried out.
To verify that the Mainframe Sales Processing Subsystem accurately processes sales data,
creates reports, and upholds data integrity.
Page 3 of 7
Test Strategy Template v1.4 (2021)
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Test Strategy
-
SystemFusion
SQL database:
The purpose of testing is to verify the architecture of the data warehouse,
including the procedures for loading, extracting, and transforming data. The verification of
data storage architecture and fundamental data integrity tests will be carried out. Data
transformations, aggregations, and the process of importing data from diverse sources will all
be the subject of testing.
Non-functional characteristics:
1.
Performance:
How fast the system responds in different loads.
2.
Reliability:
To check if the system would not end in failure if concurrent operations are
done.
3.
Availability:
To make sure the system is always available to be used and to see how
much time it takes to get up after a failure.
4.
Security:
To make sure that the user data is safe and secure.
5.
Usability:
The system should be easy to use.
6.
Compatibility:
The system should work on different browsers, OS, etc.
Complexities and Challenges:
1.
COBOL
Sales Processing Subsystem: It may have complex logic that might be difficult
to test and the number of tools that are available to test such legacy systems are few.
2.
SQL Database: Database System involves the extraction, transformation, and loading of
data from various sources that can be time-consuming.
3.
Integration of Multiple Sub-Systems: The integration of multiple sub-systems, such as the
Sales Data Entry System, Sales Processing Subsystem, and Database, can present
challenges like data consistency, synchronization, and end-to-end process flow.
Other Risks:
Technical Complexity: Multiple systems and technologies, including Java, JavaScript,
COBOL, SQL Server, and Python, are being integrated as part of the project. There is a
danger of technical difficulties, compatibility problems, and greater development and
testing work due to the complexity of maintaining and assuring flawless integration
among these various systems.
Benefits:
1.
Improved Business Decision Making:
After using data, the organization can make
better decisions in future.
2.
Improved Sales Data Entry:
The stores' entry of sales data will be streamlined by the
web-based data entry system, resulting in accurate and reliable reporting. As a result, data
quality will be better, sales performance will be better tracked, and sales reports will be
more trustworthy.
Page 4 of 7
Test Strategy Template v1.4 (2021)
Test Strategy
-
SystemFusion
Testing Standards:
ISTQB Standards:
The project will adhere to the rules and principles established by
the ISTQB, which offers a thorough foundation for software testing procedures,
methods, and terminology.
Agile Testing:
The project would be managed to utilize an Agile strategy. Iterative
testing, continuous integration, and early defect detection are examples of agile
testing principles that will be used to ensure regular feedback and flexibility in
response to shifting needs.
Test Documentation
: To ensure traceability and promote efficient communication
among project stakeholders, the project will maintain the necessary test
documentation, including test plans, test cases, test scripts, and test reports.
5
Deliverables / Procedures
Planned Test Deliverables:
1.
Test Plan:
The test plan is a thorough document that details the general testing strategy,
goals, range, and dates. It outlines the methodology, resources, and testing strategy
allotted to each testing phase. The test plan's objectives are to serve as a road map for
testing operations and to guarantee that they are in line with project objectives.
2.
Test Cases:
Each test scenario's inputs, anticipated outputs, and conditions for execution
are specified in great detail in test cases. These test cases offer extensive test coverage by
covering a variety of functional and non-functional requirements. The goal of test cases is
to give testers precise instructions on how to carry out the tests and verify system
functionality.
3.
Test Reports:
Test reports provide an overview of the outcomes of test execution,
including the number of tests. These reports provide insights into the quality of the
system under test.
Planned Procedures:
1.
Test execution:
It entails running test cases and test scripts in order to verify system
functionality.
2.
Test Review Meetings:
Test review meetings are held to review and discuss the test
findings, pinpoint any trouble spots, and decide what to do next. To ensure
collaboration and alignment in resolving test findings, these sessions engage
stakeholders.
6
Suspension / Resumption & Exit Criteria/Conditions
Planned Test Suspension Criteria:
Page 5 of 7
Test Strategy Template v1.4 (2021)
Test Strategy
-
SystemFusion
Critical Defects:
If critical flaws are found that seriously affect the system's
functioning or stability, testing may be put on hold. The performance, security, or
user experience of the system is highly at risk from critical flaws. Testing has
been put on hold to give the development team more time to concentrate on
resolving pressing problems.
Environment Concerns:
Testing may be put on hold if there are problems with
the test environment that limit appropriate test execution or jeopardize the
reliability of the findings. For instance, it can be essential to stop testing until the
test environment is returned to a proper state if it becomes unstable, inaccessible,
or encounters technical issues.
Planned Test Resumption Criteria:
1.
Defect Resolution
: Testing can continue when critical flaws found during testing have
been fixed and verified. The development team must attest that the key problems have
been fixed and that the affected functionality has been properly retested.
2.
Stability of the test environment:
Once any issues with the test environment, such as
infrastructure or network issues, have been fixed and the environment is deemed stable
and appropriate for testing operations, testing can resume.
Expected Test Exit Criteria:
1.
Test Coverage and Completion:
The tests should appropriately cover all identified
functional and non-functional requirements while adhering to the defined objectives. This
entails confirming that all crucial system components and operational procedures have
been tested.
2.
Evaluation of Test Results:
Test results must be assessed in relation to pre-established
success criteria, such as pre-established acceptance criteria or performance standards.
Thresholds for response times, system accessibility, or data accuracy may be among these
requirements.
3.
Stakeholder Agreement:
Important parties, including project managers, business
representatives, and quality assurance teams, should be involved in the decision to end
testing and go on to production. These parties involved should study the overall test
results, assess the system's preparedness, and decide whether to proceed after reaching an
agreement.
7
Approvals
Roles and Responsibilities
Role
Name
Organization/
Position
Contact Information
Sign
off
Comment
s (Y/N)
Project
Gaganjot
Best Sell
gagan@bestsell.com
GS
Y
Page 6 of 7
Test Strategy Template v1.4 (2021)
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Test Strategy
-
SystemFusion
Manager
Singh
Business
Analyst
Emily
Adams
Best Sell
emilyad@bestsell.co
m
EM
Y
QA Analyst
Sarah
Roberts
Best Sell
sarahrb@bestsell.co
m
SR
Y
Developmen
t Lead
Lisa
Clark
Best Sell
lisacl@bestsell.com
LC
Y
CEO
Mary
Wilson
Best Sell
marywil@bestsell.com
MW
Y
Sign-off:
(“Signatures” of all above stakeholders.)
Comments:
(Include space here for specific comments/concerns/suggestions from stakeholders):
References :
Textbook:
Advanced software testing(vol 1) - Rex Black
Page 7 of 7
Test Strategy Template v1.4 (2021)