Welcome To
GR09
Presentation
Basil Bayaa
Youssef adbya
Project WEB Testing
Product:
Pet Shop
�
Introduction
In the last few years more & more people in word care about animals & prefer to have a pet in home so many of pet shop are opening all over the word also the home delivery culture is taking a very large area among the young couples so to keep up with the new needs more pet shops go online to cover the needs of the growing market.
S T P�Software Test Plan
Testing approach
The testing team will work according to the STP document , In order to meet deadlines.
Resources: 2 testers. A total of 2 staff members will be assigned to this project
The test site is split, the tests will be conducted in Haifa, Ebelin.
Hardware / Software the Team Needs: 2 Smartphones, 2 PC.
The STP will be divided into 2 epics for each tester, Web & Phone testing, and based on it, we will start the STD document.
Once the STD document is done, 4 rounds of testing will be performed for each tester, 2 for Web & 2 for Phone, At the end of which an STR document will be submitted.
Relevant documents
The following is a list of documents relevant to the preparation of this document:
Entry and exit criteria�The following is the table of entry and exit criteria for each level of testing in this version:
Level of testing | Entry criteria | Exit criteria |
SYSTEM |
|
|
S T D�Software Test Design
Basil Bayaa - S T D
Basil Bayaa - S T D
Basil Bayaa - S T D
[GR09] - BASIL - 3 - Test Cases for Category screen (Functional) - in - ANDROID 11 - Galaxy S10e - Google Chrome APP - 103.0.5060.129 |
|
[GR09] - BASIL - 4 - Test Cases for Subcategory screen (Functional) - in - ANDROID 11 - Galaxy S10e - Google Chrome APP - 103.0.5060.129 |
|
[GR09] - BASIL - 5 - Test Cases for Server Side Testing - CATEGORY SCREEN |
S T D - basil�
Youssef Adbya - STD
QASE�Run Tests & DEFECTS Reporting
Basil Bayaa - TEST CASES -> TEST
>
Basil Bayaa - TEST CASES -> TEST
>
Basil Bayaa - TEST CASES -> TEST -> STEPS
>
Basil Bayaa - RUN TEST
Basil Bayaa - RUN TEST -> ISSUE-> BUG REPORT
Basil Bayaa - DEFFECTS
Basil Bayaa - DEFFECTS
Youssef adbya - TEST CASES -> TEST
[GR09] youssef- When user press "confirm" to the shipping detaials the website will charge the updated card & open the cahrge details wich included(type ,number , expiration date of the card)
Youssef adbya - RUN TEST
Youssef Adbya - DEFFECTS
Youssef Adbya - DEFFECTS
S T R�Software Test Rsults
Relevant documents
The following is a list of documents relevant to the preparation of this document:
activity | planning | Performance | Reason for difference | The effect of the difference |
STP | 05.08.2022 | 08.08.2022 | Weekend | Work more hours to finish in time |
STD | 10.08.2022 | 11.08.2022 | Working of the STP | In this stage didn’t think that the delay will effect the plan |
Running Tests on PC WEB & opening issues (QASE) | 16.08.2022 | 18.08.2022 | The delay in STD & the fact off delay one day before | We work in midnight also |
STR | 19.08.2022 | 20.08.2022 | The delay is more shorter now | We kept our strategy in working in midnight |
Presentation | 23.08.2022 | 23.08.2022 | | |
Differences in other activities
Executive summary
In this project we chose 4 epics :�1) Category screen 4.5 – included 20 test cases
2) Subcategory screen 4.6 – included 18 test cases
3) Order details summary screen 4.11 – included 13 test cases
4) Order confermation screen 4.12- included – 19 test cases
We planned to run 100% of the tests 2 times (one on P.C and another run on Mobile)
In fact we were able to run 95% of the tests (67 test run 3 didn't) because the fact that 3 test was blocked .
From the result we can assure that the website is similar even if the user open it in Mobile or P.C
In Category screen we design 20 tests – 14 tests passed 6 bugs
In Subcategory screen we design 18 tests – 16 tests passed 2 bugs
In Order details summary screen we design 13 tests – 8 passed ,4 bugs ,1 blocked
In Order confermation screen we design 19 tests – 13 passed , 4 bugs , 2 blocked
Total : 70 tests – 51 passed , 16 bugs , 3 blocked
Summary of test results
Our project is done by 2 staff members each one of us take 2 epics and follow the requests that was in Characterization document. the common parts in the project we divided equally to finish the job in time.�results:�1. We run 70 test cases 2 times (one in P.C & one on Mobile) the results was the same�2. From 70 test cases we had 16 bugs (in mobile runs and also in P.C runs) and 3 blocked.
3. We found 1 critical bug but all the other bugs was normal
Known faults
Below is a summary of the faults discovered in this version, according to the status of the fault and its degree of severity:
Environment | Fault Status | Critical | High | Normal | Low | Total |
P.C | In progress | 1 | 0 | 15 | 0 | 16 |
Mobile | In progress | 1 | 0 | 15 | 0 | 16 |
Total : 70 tests
51 passed - BLUE ,
16 bugs- RED ,
3 blocked - YELLOW
Conclusions and lessons learned
Here are the conclusions and lessons learned during the testing process of this version.
These conclusions and lessons will be used to improve the testing process in future versions:
● Reading the relevant documents, until full understanding.
● Concentrate the test and bugs into areas, so that we can work by area and not scattered.
● Review the test cases that did not pass, as there is a possibility that we did not use the new tool for testing, QASE, the right way.
● Understand the web requirements, for knowing how to sort the bug level (critical, high, normal…) correctly.
● Update any bug opened in QASE so that there is no miss in a particular bug and waste time repeating test cases that have already been tested.
Thank You for watching