Homework 7 - TaaviGilden/The-Team GitHub Wiki
Task 1
Task 2
Taking an order
Test case ID: 1
Related requirements: Creating orders
Input: 1 x Saku Originaal, 2 x A’leCoq Premium
Steps performed during the verification process: Create new order -> Add all the items listed (Saku Originaal, A’leCoq Premium) with the right quantities (1x, 2x) -> Confirm the order -> fill out the payment fields -> Accept order
Expected results: The order has been saved to the history with a timestamp and user can see the order details, ordered items are added to the receipt, warehouse state is updated accordingly
Have multiple orders open at any time
Test case ID: 2
Related requirement(s): Creating an order, modifying an order.
Input: First order: 2 3-course lunches. Second order: 1 beer.
Steps performed during the verification process: An order is created for 2 3-course lunches to be paid at the table. Before the first order is completed, another is created for 1 beer, payed by the counter.
Expected results: The order which was created first must still be open after another order has been completed and must still be modifiable.
Updating the quantity of an existing item in the warehouse
Test case ID: 3
Related requirement(s): Adding items to the warehouse
Input: An additional amount of 100 beers is transported to the restaurant.
Steps performed during the verification process: A worker adds 100 to the quantity of beers in the warehouse by clicking “Add item” and then filling the fields to match the ID of the beers.
Expected results: The amount of the beers increases by 100.
Search history item by date and the total sum
Test case ID: 4
Related requirement(s): Searching items from history
Input: History item details: date(23/11/13), total sum(10.30€)
Steps performed during the verification process: Worker opens history tab in the system -> searches for all the orders with the date(23/11/13) and total sum of 10.30€ -> clicks on the order for more details
Expected results: If the input information is valid the system will show all the orders with given criteria.
Split bills into smaller bills
Test case ID: 5
Related requirements: Split bills into smaller bills, create orders
Input: Bill with the following items: Saku Rock x 2 , Walter x 5. Lets call it bill 1 We have 2 clients. Client 1 ordered Saku Rock x2. Client 2 ordered Walter x 5.
Steps performed during the verification process: Click the “Split the bill” button.A new bill is created. Lets call it bill 2. The user adds all the items from client 1 (Saku Rock x 2 ) to bill 2. Another new bill is created. Lets call it bill 3. The user adds all the items from client 2 (Walter x 5) to bill 3. Bill 1 is automatically deleted and bill 2 is renamed to bill 1 and bill 3 is renamed to bill 2.
Expeced results: The bill is split into n subbills. The payments for the subbills can be processed separately.
Task 3
Usability
System must run on UNIX/Windows.
We test the system on all the Windows versions and see whether the functionalities work. We test the system on three of the most popular UNIX distros and see whether the functionalities work. Functionalities are tested by developing specific use cases, which encompass every single usable functionality. The test is considered successful when all functionalities work.
System must be usable by people with visual impairments.
We see if all the text font size is big enough for everyone to read with ease. Also have to check if all the buttons and text contrast well enough from the background. To see whether it is acceptable to people with visual impairments, we recruit up to 10 random candidates to try out the system, who meet our criteria of visual impairments. If they have no complaints, we can consider the system to be usable.
Performance
System must handle up to 1000 simultaneous users.
To test this non-functional requirement, we will be using a tool called Blitz, which allows us to simulate up to 50 000 virtual users on our system. We will be testing the system with 1000 users, if all the actions still take less than 1 second to complete on average, the test can be considered successful.
System should turn on in less than 1 minute.
To test if the system turns on in less than 1 minute we test it on a virtual machine 5000 times and get the average turn on time.