Test plan for comp3780. every group needs to have one PDF

Preview

Summary

Our project is to create an Ai survey tool on the existing Wix website
which will help a customer see how their business is doing and If theyneed to fix a particular area in their business to grow and improve. The
tool will consist of 8 different sections and 4 questions in each section....

Description

Test plan Group 41

[Company address]

Red is Chris Green Faraan Blue John

Table of Contents 1. Introduction 2.

System Architecture 2.1 Inside scope Definition 2.2 Out of scope Definition

3.

Testing Strategy 3.1 Unit testing 3.2 System and Integration testing

3.3 Performance testing 3.4 User Acceptance testing 3.5 Regression testing 3.6 Usability testing

4.

Hardware Requirements 4.1 Computers 4.2 Architecture 4.3 Processing Power 4.4 Memory

5.

Environment Requirements

6.

Testing Schedules 6.1 Weekly Testing 6.2 Fortnightly Testing 6.3 Project End Testing

7.

Control Procedures 7.1 Problem reporting

8.

Roles and Responsibilities

9.

Deliverable Schedule

10.Depen dencies 11.Risks Assessm ent 12.Tools 13.Appen dix 13.1 Acronyms and Abbreviations

1. INTRODUCTION Our project is to create an Ai survey tool on the existing Wix website which will help a customer see how their business is doing and If they

need to fix a particular area in their business to grow and improve. The tool will consist of 8 different sections and 4 questions in each section. At the end the survey will generate a percentage which will give them a score on how well or poorly there business is doing.

An AI survey[SF01]: This survey will begin by requesting details from the user to input before starting the survey which will get stored into the database. The survey consists of 9 sections each highlighting a different aspect of a business. The selection the user makes will get transformed into a percentage and calculated. Based upon the result, the customer will receive a specific response to how well or how poorly his business is performing. The customer can further request to get in contact with one of our representatives by filling out a small form.

2. SCOPE 2.1 Inside scope:

The system requirements in the SRS are going to be tested. We will test these requirements using Unit testing,performance testing, Usability testing and QA testing.

2.2 Out of scope: We are not responsible for anything else on the website and we will test the survey and that the users details are reaching the database

3. TESTING STRATEGY This Project is following an agile approach to development and so at the end of every week, the system will be tested. The weekly testing will focus on unit, regression, performance and integration testing, with usability and acceptance testing being performed fortnightly as they will likely be more involved processes.

3.1 Unit Testing

Definition

This is usually performed by the developer. It is used to verify a particular module of a unit or a particular. To ensure that they are working according to specifications. This is the basic level of testing.

Methodolog y

Each group member will be responsible to test the features of the survey to see that each function performed from the test cases has valid / invalid inputs. It will be used to test the functionality. ]

3.2 System and Integration Testing

Definition

This builds on unit testing and integrates different components or modules into an active functioning system. Each unit must be tested to ensure its components are successfully integrated and tested otherwise a software platform won’t have any value.

Methodol ogy

This will build on from unit testing it will make our integration testing more relaxed. Our system is a survey based on Wix Platform which has multiple sections that consist of multiple questions. From the answers of the survey it will generate results and percentages. We will ensure that each functionality is thoroughly checked. This will be performed by Faraan our testing analyst by using the test scripts.

3.3 Performance Testing

Definition

Performance Testing is where the performance of the system is measured. This performance includes this like loading times and response times which are measured and compared to the times listed in the requirements.

Methodol ogy

Describe how Performance & Stress testing will be conducted. Who will write the test scripts for the testing, what would be the sequence of events of Performance & Stress Testing, and how will the testing activity take place? Performance testing will be performed using automated scripts that will time how long it takes to complete a given action and compare it the requirement and give a pass or fail for that requirement. The testing manager will write the required scripts and then perform these tests.

3.4 Usability testing

Definition

Usability testing is carried out by all users of the platform. This will ensure the easy of performance and accuracy of on screen buttons. It verifies the presentation of screens standards, structures and consistency across all of screens

Methodolo gy

Usability testing is very important for our project we will ensure that we are consistent across all screens ensure the performance and buttons are functioning according to our specifications. This will be tested to ensure that our quality is high and we are meeting our clients needs.

3.5 QA Testing

Definition

Quality Assurance testing is ensures that each and every function is working properly before it is released on the live environment. It is tested in the developing and live environment.

Methodol ogy

We will be testing our final product both in the testing and live environment to ensure that each function is working before we release it to the live environment and hand it over to our client. We will test in in different browsers, Ipad and Android.

4. HARDWARE REQUIREMENTS 4.1 Computers: The team will use the member's home computer for testing. Any computer that can open the browser normally can be used.

4.2 Architecture The team does not need any architecture on the hardware. Engineers will test on the software architecture.

4.3 Processing power The development and testing of the website does not require its powerful hardware. The processor can be arbitrarily selected from intel's i3, i5, i7.

4.4 Memory

The browser may take up a lot of memory in the test, especially when multiple pages are open at the same time, and the test just needs to open multiple pages for comparison and record data. So we recommend use computers which RAM above 4GB capacity for testing (including development).

5. ENVIRONMENT REQUIREMENTS Hardware: 2GB RAM + Intel Core i3 Processor Software: browser (Google Chrome, Safari, etc.)

6. TESTING SCHEDULEs Include test milestones identified in the Software Project Schedule as well as all item transmittal events. Define any additional test milestones needed. Estimate the time required to do each testing task. Specify the schedule for each testing task and the test milestone. For each testing resource (that is, facilities, tools, and staff), specify its periods of use.

6.1 Weekly Testing:

All the tests are being performed weekly on a thursday before the meeting with the client to ensure the product is well presented and to inform them of any setbacks. Mostly unit testing is being performed as it is very precise alongside performance testing to ensure survey buttons are working smoothly.

6.2 Fortnightly Testing:

We will be doing our tests weekly so there isn't a need for new type of test to be performed on a fortnightly basis

6.3 Project End Testing:

User acceptance testing and usability will be performed at the end of the project as both will determine how well the project is designed and if there is any feedback so that we can do any last minute changes

7. CONTROL PROCEDURES 7.1 Problem Reporting

Document the procedures to follow when an incident is encountered during the testing process. If a standard form is going to be used, attach a blank copy as an

“Appendix” to the Test Plan. In the event you are using an automated incident logging system, write those procedures in this section.

As we are using WIX as our platform if any errors do occur we report to the company itself to fix the issue. In the case of our survey not performing tasks like we require, our team takes notes of what is going wrong and then look into making it functional. The tests like usability testing and performance testing will be carried out after the update is made to ensure the problem has been resolved.

8. ROLES & RESPONSIBILITIES Team Member

Testing Role

Faraan Mirza

Testing Manager/ Responsible for overseeing all testing, helping with UnIt testing, integration testing,QA testing and Usability Testing.

Daniel Braine

Software Developer/ Assistant Test Manager Responsible for writing and maintaining tests and test cases.

Qingyuan Zhang

Software Developer Responsible for writing and maintaining all test cases

John Noujain

Software Developer, Responsible for writing and maintaining all test cases

9. DELIVERABLE SCHEDULE Major Deliverables

Deliverable

Team Member Responsible

Date Due

Test Plan

Faraan Mitza

23/10 increment 4

Test Cases

Faraan Mirza, John Noujaim

23/10 increment 4

Test Incident reports

Qingyuan Zhang

Weekly starting 9

Test Summary Reports

Faraan Mirza, Daniel Braine

23/10 increment 4

10. DEPENDENCIES Testing will be done as we go as we have a tight schedule and need to stay on top of everything. There may be a bit of drawbacks in our project.

11. RISKS/ASSUMPTIONS The project encounters new requirements, which may affect other progress of the project. The team will contact the sponsor and contact the relevant matters to ensure that time is properly allocated during the work period. Errors that may be caused by the testing process. Any increase or decrease in code will affect the integrity of the entire product, and development tools do not have backtracking capabilities. The team will back up the test-qualified code content to avoid this.

12. TOOLS The test will be conducted by the preview function provided by the wix website. It visualizes the way the site is done in the quickest way. We used google docs to share experimental data, development progress, and all possible design documentation.

13. Appendix

The Lead Icon Wix Corvid API Macquarie University...