0% found this document useful (0 votes)
27 views9 pages

ACC Test Plan

Uploaded by

Yosef Kitaw
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
0% found this document useful (0 votes)
27 views9 pages

ACC Test Plan

Uploaded by

Yosef Kitaw
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/ 9

American Car Center(ACC) MVP

Test Plan for Sprint 2

MARCH 15, 2022


Depalma Studio

Test Plan For ACC Projcet


Table of Contents

Contents
1. Introduction........................................................................................................................................3
1.1. Purpose.......................................................................................................................................3
1.2. Objective.....................................................................................................................................3
2. Scope...................................................................................................................................................3
2.1. Features to be Tested.................................................................................................................3
2.2. Features not to be Tested...........................................................................................................5
3. Approach.............................................................................................................................................5
3.1. Test Strategy...............................................................................................................................5
3.2. Test Levels...................................................................................................................................5
a) Functional Testing...........................................................................................................................5
b) Usability Testing..............................................................................................................................6
c) Browser Compatibility Testing........................................................................................................6
d) Accessibility Testing........................................................................................................................6
e) GUI Testing......................................................................................................................................6
f) Performance Testing.......................................................................................................................6
g) End- to- End Testing........................................................................................................................7
3.3. Suspension Criteria and Resumption Requirements..................................................................7
3.3.1. Suspension Criteria.................................................................................................................7
3.3.2. Resumption Requirement.......................................................................................................7
4. Environment........................................................................................................................................7
5. Deliverables........................................................................................................................................8
6. Test Schedule......................................................................................................................................8
7. Responsibility......................................................................................................................................8
Definitions and Acronyms...........................................................................................................................8
Reference....................................................................................................................................................9

Test Plan For ACC Projcet


1.Introduction
1.1. Purpose

The purpose of this test plan document is to provide details on how testing
process will be conducted and describe the scope, objective approach, resource,
and testing schedule for American Car Center MVP project. This document will
mainly contain Objectives: This section contains the testing objectives. Scope: In
this section, features to be tested and features not to be tested will be identified.
Approach: In this section, the test approach and the tools that will be used for
this project will be mentioned.

1.2. Objective
The main objective of the testing is to:
 Deliver a System/ project that meets customer requirement;
 Maintain the quality of the system;
 Ensure the MVP features of American Car Center project has been started
 To set expectations and align the team for success throughout the entire
testing process.
 To check ACC project follow a responsible web design.
 Evaluate User experience of the application satisfies customer requirement
(i.e. Look like to client Figima Design ).

2.Scope
2.1. Features to be Tested
Both functional and nonfunctional Requirement of American Car Center project will be
going to tested.

Test Plan For ACC Projcet


Functional requirements define the basic system behavior. Essentially, they are what the
system does or must not do, and can be thought of in terms of how the system responds
to inputs. Functional requirements usually define if/then behaviors and include
calculations, data input, and business processes.
The following functional requirement of requirement of ACC project going to be
tested.
 Home page of ACC which contains head with menu, main body with
sections and Footer with its owns information and links.
 Header and footer (entire page).
 FAQS page which include different list of FAQS with filtering
functionality.
 About us that include basic information about ACC and FAQS
 Privacy notice page, privacy policy
 Vehicles Search, filter with different parameters
 Car Details include with all necessary information like car photo, model

Nonfunctional Requirements (NFRs) define system attributes such as


Security, reliability, performance, maintainability, scalability, and usability and page
responsibility. Also known as system qualities.
In ACC project most Nonfunctional requirement are going to be tested
Such as: -

 Portability and compatibility. Which hardware, operating systems, browsers,


and their versions does the software run on? Does it conflict with other
applications and processes within these environments?

 Reliability, availability, maintainability. How often does the system experience


critical failures? and how much time is it available to users against downtimes?
 Security. How are the system and its data protected against attacks?
 Localization. Does the system match local specifics?
 Usability. How easy is it for a customer to use the system?

Test Plan For ACC Projcet


2.2. Features not to be Tested
Other than mentioned above in section 2.1.

3.Approach
3.1. Test Strategy
In ACC Project, system testing activities that includes functional and non-
functional testing which are required for Content management system (CMS) will
be conducted. In addition to this, a thorough testing of every input in the
application to check for desired outputs and tests the design and behavior of the
system/application will be conducted.
To determine if all features within the system/application are performing as
expected and to confirm that the system satisfies customer requirements, test
cases and test check lists will be prepared for different test types. In the test case
design process, it is anticipated to use different testing techniques like Boundary
Value Analysis technique, Decision Table technique, State Transition technique or
Equivalence partitioning technique based on the input value of the forms in the
Application. Using free testing tools and plugins will also be used to improve
accuracy.

3.2. Test Levels


Below is list of test types intended to be conducted for the ACC project.
a) Functional Testing
Functional testing checks an application, or system to ensure that it is
doing exactly what it is meant to. In this testing, each function of the
system/application will be tested, by providing appropriate input and
verifying the output against the requirements.

Test Plan For ACC Projcet


b) Usability Testing
It is a testing method for measuring how easy and user-friendly a software
application is. In this testing, how easy a design is to use is going to be
tested based on the “QA check list” document prepared by Excellerent IT
Solutions.

c) Browser Compatibility Testing


This testing emphasis on availing an application's basic features and
functionality to users on different browser-OS combinations, devices, and
assistive tools. For this project, it is intended to use free compatibility
testing tool/plugins such as Browsershots, BrowserStack,
CrossBrowserTesting, …etc to conduct browser compatibility test.

d) Accessibility Testing
Accessibility testing is the practice of making a system/application usable
to as many people as possible. It will increase the user’s satisfaction and
will also contributes a lot towards the success of a business as we work to
get the application accessible to each and every user.

e) GUI Testing
This testing type checks the Graphical User Interface of the Software. And
its main purpose is to ensure the functionalities of software application
work as per specifications by checking screens and controls like menus,
buttons, icons, etc.

f) Performance Testing
Performance testing is a testing measure that evaluates the speed, security ,
responsiveness and stability of a computer, network, software program or device under
a workload. Organizations will run performance tests in order to identify performance-
related bottlenecks.

Test Plan For ACC Projcet


Performance requirements should be identified and tested. Typical parameters include
processing speed, data transfer rates, network bandwidth and throughput, workload
efficiency and reliability.
g) End- to- End Testing
End-to-end testing is a Software testing methodology to test an application
flow from start to end. The purpose of End to end testing is to simulate the
real user scenario and validate the system under test and its components
for integration and data integrity . It simulates the real user scenario the
Red Zone project application is going to be tested from beginning to end
process.

3.3. Suspension Criteria and Resumption Requirements


This section will specify the criteria that will be used to suspend all or a
portion of the testing activities on the items associated with this test plan.

3.3.1. Suspension Criteria


Testing will be suspended if the incidents found will not allow further testing
of the system/application under-test. If may lack the availability of external
dependent components during execution, or when a defect is detected which
may restrict the testing process to proceed further .and if any of the tests
selected by the member do not give the expected result, then the testing will
be suspended until the bug is fixed.

3.3.2. Resumption Requirement


Resumption of testing will be possible when the functionality that caused the
suspension of testing has been retested successfully.

4.Environment
 Hosting: on Google Cloud or Microsoft Azure .
 UI with React JS.

Test Plan For ACC Projcet


 Back end with strapi 4.0.

5.Deliverables
 Test Plan Document
 Test Cases and test suite
 Test Incident Report
 Test Summary Report

6. Test Schedule
Since the methodology is Agile it is a bit difficult for us to put time for each task. ACC
Project has 2 week sprint and sprint has been started on 03/21/ 2022. Below are the
tasks that will be undertake for the testing process the project.
 Understand customer requirements
 Prepare Test Plan
 Write test cases
 Prepare test data
 Execute testing
 Identify problem areas and add them to a tracking system
 Discuss fixes with developers
 Prepare Incident Report
 Prepare Summary Report

7. Responsibility
Since there is only one QA in a team and have high responsibility to work forward to
success of the project.

Definitions and Acronyms


The following list will help the team to handle different terms and definitions:
• QA = Quality Assurance
• DEV = Development
• AC = Acceptance
• ACC= American Car Center
• CMS = Content Management System
• FAQs= Frequently Asked Questions
• MVP = Minimum Valuable Product

Test Plan For ACC Projcet


• PO = Product Owner
• CI/CD= Continuous Integration / Continues Deployment
• API = Application Programing Interface
• UI = User Interface

Reference
1. ACC Test Strategy Template Document
2. IEEE Test Strategy Outline FORMAT

Test Plan For ACC Projcet

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy