|
|
**Action Plan:**
|
|
|
|
|
|
Zhang and Zhong finishes the part of introduction, Scope. (Actual: 1 hour). Li and Liu finishes the part of quality objective.(Actual: 0.75 hour). We also identify roles and responsibilities for each group member(Actual: 0.4 hour). We finishes the test methodology and inspection methodology together.(Actual: 1.5 hours). As for the next milestone, we will write the code for implementation of 2-3 epics and testing should have occurred by this data.(Estimate: 6 hours)
|
|
|
|
|
|
**Introduction:**
|
|
|
|
|
|
Our project aims to do a website for a cat cafe. This is a group project which means we have more than one member to finish designing. As a result, the quality assurance will be the outcome of a teamwork. The strategies are following
|
|
|
|
|
|
A.We will test(unit test and regression test) most functions that we write by inputting right value, wrong value and even some extreme value.
|
|
|
|
|
|
B.We will try to ask our friends and post some online researches to make sure that our website.
|
|
|
|
|
|
C.We will focus on the coding style and make sure code fits the software goal(correct, efficiency, robust, adaptable, reusable).
|
|
|
|
|
|
D.We will make sure that each requirement is satisfied.
|
|
|
|
|
|
E. We will add doc string when writing each function.
|
|
|
|
|
|
F.We will ask professor and TA suggestion regularly.
|
|
|
|
|
|
**Scope:**
|
|
|
|
|
|
Function(checked):
|
|
|
|
|
|
Google_weather: check whether it can google the weather information
|
|
|
|
|
|
place_order: check whether customer can place the order
|
|
|
|
|
|
add_order: check whether customer can add items to order
|
|
|
|
|
|
send_info: check whether send the information to the database
|
|
|
|
|
|
get_info: check whether can get customer information
|
|
|
|
|
|
add_cart: check whether can add items to shopping cart
|
|
|
|
|
|
remove_cart: check whether can remove items to shopping cart
|
|
|
|
|
|
clear_all: check whether can clear all the information
|
|
|
|
|
|
Function(not be checked):
|
|
|
|
|
|
Display_order: The web page is able to display the order information.
|
|
|
|
|
|
**Quality Objective:**
|
|
|
|
|
|
Our project is making a website. The object is that customers can place their orders online and store will get all the necessary information about this order. The marker will run our code and no bugs.
|
|
|
|
|
|
**Roles and Responsibilities of team members:**
|
|
|
|
|
|
Liu is the leader who manages our work in our group. Li is the developer. Liu and Li focus on how to connect the database with our website.
|
|
|
Zhang and Zhong are the reporter and designer who always report what’s our current progress and design the website.
|
|
|
|
|
|
**Test methodology:**
|
|
|
|
|
|
Background information: We will both do a regression test and unit test.
|
|
|
|
|
|
|
|
|
Test add_order
|
|
|
|
|
|
Usage: Used to add order of coffee (purchase coffee)
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click the button of add_order
|
|
|
|
|
|
Post-Condition: The output(price and quantity of coffee) should be displayed to user and the calculation should be correct
|
|
|
|
|
|
|
|
|
Test remove_order
|
|
|
|
|
|
Usage: Used to delete order of coffee (cancel coffee)
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click the button of remove_order
|
|
|
|
|
|
Post-Condition: The output(price and quantity of coffee) should be displayed to user and the calculation should be correct
|
|
|
|
|
|
|
|
|
Test google_weather (Google_weather, recommend_item)
|
|
|
|
|
|
Usage: Use to display the recommendation of coffee based on Weather
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click and enter the homepage
|
|
|
|
|
|
Post-Condition: The output should display appropriate coffee and grab the accurate local weather to users
|
|
|
|
|
|
|
|
|
Test Cancel button
|
|
|
Usage: Used to cancel wrong order
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click the cancel button
|
|
|
|
|
|
Post-Condition: The wrong order should be canceled after clicking
|
|
|
|
|
|
|
|
|
Test get_info and send_info
|
|
|
|
|
|
Usage: Used to get and record user information
|
|
|
|
|
|
Pre-Condition: Input for name should be string, phone number should be int,order number should be int or string
|
|
|
|
|
|
Action: Click the button of getting user information and send it to database
|
|
|
|
|
|
Post-Condition: All user information typed by user will be recorded to the database
|
|
|
|
|
|
|
|
|
Test place_order button
|
|
|
|
|
|
Usage: Used to place order when user finished choosing
|
|
|
|
|
|
Pre-Condition: No
|
|
|
|
|
|
Action: Click the button of place order
|
|
|
|
|
|
Post-Condition: The website should tell user his/her order is successfully placed and return a order number to user.
|
|
|
|
|
|
|
|
|
Test add_cart
|
|
|
|
|
|
Usage: Used to calculate the final price and quantity after add all coffee
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click the button of add_cart
|
|
|
|
|
|
Post-Condition: The output(price and quantity of coffee) should be displayed to user and the calculation should be correct
|
|
|
|
|
|
|
|
|
Test remove_cart
|
|
|
|
|
|
Usage: remove what customers currently have in the shopping cart
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click the button of remove_cart
|
|
|
|
|
|
Post-Condition: The output(price and quantity of coffee) should be displayed to user and the calculation should be correct
|
|
|
|
|
|
|
|
|
Test clear_all
|
|
|
|
|
|
Usage: Used to clear all information
|
|
|
|
|
|
Pre-Condition: None
|
|
|
|
|
|
Action: Click the button of clear_all
|
|
|
|
|
|
Post-Condition: all information will be deleted(empty) |
|
|
\ No newline at end of file |