A smart phone application
for sales agents
Testing Document
Academic Advisor:
Prof. Ehud Guddes
Professional Advisor:
Mr. Bernard Fadlon
Developers:
Arsen Shatikian, Udi Vaksman, Avihai Danino
Testing User Interface:
Test ID Goal Description
1 Validating that the GUI starts on Run the app and see that the first
login page. page is login page.
2 Validating that if incorrect user On the "login" screen enter incorrect
name or incorrect password is username or incorrect password and
entered, User cannot login. see that "Login Failed" message is
shown.
3 Validating that if correct user On the "login" screen enter correct
name and password is entered, username and password and see that
User is logged in successfully. "Search Customer" screen is shown.
4 Validating that if we are searching On the "Search Customer" screen enter
an exist customer at the "Search a ID or a name of the customer and see
Customer" screen, we are getting that we got the customer on the list of
him as a result at the "Found the result.
Customer" screen.
5 Validating that if we are searching a On the "Search Customer" screen enter
customer that doesn't exist at the a ID or a name of a customer that
"Search Customer" screen, we are doesn't exist and see that we got an
getting an empty list at the "Found empty list as a result.
Customer" screen.
6 Validating that we can add\edit a On menu, we choose "customer" and
customer. choose "New/Edit", filling the fields
and see that we get "Customer Added"
message with the customer details.
7 Validating that we can see the On "Found Products" screen we click on
details of a chosen product a product and see that the "Product
Details" screen of the chosen product is
shown.
8 Validating that we can add a On "Product Details" screen we click on
product to our shopping cart "Add to Cart" button and see that "X
item\s added" message is shown.
9 Validating that we can remove a On "Shopping Cart" screen we click on
product from our shopping cart "Remove" button near the product we
want to remove and see that the
product is removed from the list.
10 Validating that we can see the On "Select Order" screen we enter the
details of an exist order order ID and see that "Order details" is
shown of the order.
11 Validating the case of nonexistent On "Select Order" screen we enter an
order ID. ID of nonexistent order and see that
error message is shown.
12 Validating the results of "Search On "Search Product" we enter some
product" attributes and check in the results that
we got the appropriate products.
13 Validating that all the history of On "orders" menu we choose "view
orders are available on "My orders" and see the list of orders on
orders" screen. "My orders" screen.
14 Validating that we can replace the On "Login" page we enter to settings
logo of the app and type a url for the logo, after saving
we can see the new logo on the
"Login" screen.
15 Validating that many users can On the screen of payment details, two
generate a same order in parallel users will press the OK button and we
can see that both of the orders are
shown on the orders list.
16 Validating that the app handles a When the user logged in we stop the
server crush server and we can see the message
"Disconnected from server" and the
app will pass to the login screen.
Testing of Non-Functional Requirements
Speed
Many users will be able to login, and the time it takes to process each of them will be tested, in
order to check the average time of login establishment.
Throughput
In order to perform the throughput tests, there is a need in many users that perform login
operations, orders, etc.. between different smartphones to the server simultaneously. Difficult to do
so in the scope of this project.
Reliability
Our system database will be accurate and will analyze all the events that were sent to the Application
server. There is no risk that several clients will try to write in the database simultaneously. If for some
reason the connection to the Application Server or to the Database Server will fall, the user will be
informed about it, and will get additional message on resumption of the connection.
Availability
The query for the products list is the longest one, it takes 125 ms. In a minute, each agent generates
2 queries, in average. If we are testing the system with 50 agents that connected to it, we can see
that in a minute, the server is busy just 5 SECONDS, and for the rest of the time it isn't busy. So for
91% of the time the server is available.
In addition, the other queries take no time for the server (close to 0 ms!!!).
Random & Automatically-generated Tests
Not applicable.