Test Cases - bounswe/bounswe2017group7 GitHub Wiki

Test Case ID: FINDING_BOOK

Test Priority: High

Test Scenario: User wants to get information about a book.

Test Purpose: To test if the bot returns the book that is asked by the user.

Designed by: Ahmet Cihat Toplutaş

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.1.1. , 1.1.2. , 1.1.4. , 1.1.6. , 1.2.1.1.1.1.2. , 1.2.1.1.1.1.5. , 1.2.1.1.4.1.

Preconditions: User is logged in to the Telegram account.

Steps Test Steps Test Data Expected Data Actual Output
1 Searching a book "Can you find me an action book?" "I have found 1723 action books. Do you want to add any more specifications or do you want to see the results?"
2 Reducing the search results. "Yes. Show me the one's that are written by Michael Crichton." "I have found 17 action books that are written by Michael Crichton. Do you want to add any more specifications or do you want to see the results?"
3 Finalization. "Show me the most popular one." "OK. Jurassic Park by Michael Crichton, http://bit.ly/2pm8gv4"

Test Case ID: RATING_BOOK

Test Priority: Moderate

Test Scenario: User wants to rate a book.

Test Purpose: To test if the bot can save the rating that is posted by the user.

Designed by: Ahmet Cihat Toplutaş

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.1.1. , 1.1.4. , 1.1.5. , 1.1.6. , 1.2.1.2.1.

Preconditions: User is logged in to the Telegram account, and starts a conversation with the chatbot.

Steps Test Steps Test Data Expected Data Actual Output
1 Specifying the action. "I want to rate a book." "OK. Which book would you like to rate?"
2 Specifying the book. "I want to rate "The Code Book" by Simon Singh." "OK. What is your rating for "The Code Book" from 1 to 5?"
3 Rating and Storing. "I rate it 4 points." "Your rating has been saved. Thank you for your feedback."

Test Case ID: COMMENT_BOOK

Test Priority: Moderate

Test Scenario: User wants to leave a comment about a book.

Test Purpose: To test if the bot can save the comment that is posted by the user.

Designed by: Ahmet Cihat Toplutaş

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.1.1. , 1.1.4. , 1.1.5. , 1.1.6. , 1.2.1.2.2.

Preconditions: User is logged in to the Telegram account, and starts a conversation with the chatbot.

Steps Test Steps Test Data Expected Data Actual Output
1 Specifying the action. "I want to leave a comment about a book." "OK. Which book would you like to leave a comment about?"
2 Specifying the book. "The book is called, "The Restaurant at the End of the Universe" by Douglas Adams." "OK. You can write your comment now."
3 Commenting and Storing. User writes the comment about the book. "Your comment has been saved. Thank you for your feedback."

Test Case ID: RECOMMEND_USER

Test Priority: Moderate

Test Scenario: User wants to have user recommendations who can give detailed information about the book s/he was searching.

Test Purpose: To test if the bot gives user recommendations (rates and comments) who is already rated the same searched book.

Designed by: Salih Sevgican

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.1.3

Preconditions: The book that user wants is recommended or rated by another user..

Steps Test Steps Test Data Expected Data Actual Output
1 Creating the query. "I'd like to get user recommendations about a book." "Allright. Which book you want to get recommendations about?"
2 Specify the book. "Lord of the Rings Two Towers written by J.R.R. Tolkien" " Here is the user recommendation whose rating for this book is similar to yours: 
Rating: 4 out of 5

Comments: This book is my favourite among the triple books of Lord of the Rings. Very deep story and everything is 
getting complicated in this one. I've read whole book in a time of breathing."

Test Case ID: FILTER_BOOKS

Test Priority: High

Test Scenario: Filtering the books with some criteria given by user while searching a book.

Test Purpose: To test if the bot correctly filters the data with some certain options given by user.

Designed by: Salih Sevgican

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.1.1.1.1

Preconditions: User must be logged in to the Telegram account and starts a conversation with the chatbot.

Steps Test Steps Test Data Expected Data Actual Output
1 Searching a book "Can you find me an action book?" "I have found 1723 action books. Do you want to add any more specifications or do you want to see the results?"
2 Try to narrow down the results. "I want to add more specifications" "Sure. What is your criterias ?"
3 Declare the specifications "Show the ones that published after 2013, cheaper than 20 dollars and english books" "I have found 23 action books. Do you want to add any more specifications or do you want to see the results?"
4 Finalization "Show the results." "OK. http://bit.ly/4tgcfv1"

Test Case ID: LOGIN_TO_WEBSITE

Test Priority: High

Test Scenario: Admin wants to login to the system.

Test Purpose: To test if the admin is able to enter the system without having trouble.

Designed by: Çağdaş Tombul

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.1, 1.2.2.1.1

Preconditions: Admin should be signed up to the system.

Steps Test Steps Test Data Expected Data Actual Output
1 Reaching the login page Admin clicks the login button Login page is opened
2 Entering the necessary data and the system Admin types what s/he needs to enter the system If s/he is authorized, s/he enters the webpage

Test Case ID: SIGN_UP_TO_WEBSITE

Test Priority: High

Test Scenario: Non-registered admin wants to sign up to the system.

Test Purpose: To test if a non-registered admin is able to sign up the system without having trouble.

Designed by: Çağdaş Tombul

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.1.2

Preconditions: Admin should have an invitation code.

Steps Test Steps Test Data Expected Data Actual Output
1 Reaching an invitation code. Admin types the invitation code to the appropriate place. The code should allow the non-registered admin to register the system.
2 Entering the necessary data and registering the system. Admin types a valid e-mail, a valid username, a valid password and retypes it. If all data is valid, s/he registers the webpage.

Test Case ID: NEW_TEMPLATE

Test Priority: High

Test Scenario: Admin wants to create a new template.

Test Purpose: To test if new template is added succesfully.

Designed by: Ebru Zorlu

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.3.1, 1.2.2.3.1.3.1.1

Preconditions: Admin is logged in to the admin panel.

Steps Test Steps Test Data Expected Data Actual Output
1 Adding a new template to a node. Admin clicks add new template. In admin panel a template box is opened.
2 Typing variables and actions. S/he types the template giving proper variables and actions. If typed values are valid, the template is ready to save.
3 Saving the template adding new template page. S/he clicks save. New template is succesfully added to conservation graph.

Test Case ID: CHANGE_ADMIN_SETTINGS

Test Priority: Moderate

Test Scenario: Admin wants to change his/her settings.

Test Purpose: To test if the admin is able to change the settings correctly.

Designed by: Çağdaş Tombul

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.2, 1.2.2.2.1, 1.2.2.2.2, 1.2.2.2.3

Preconditions: Having a valid admin account.

Steps Test Steps Test Data Expected Data Actual Output
1 Reaching profile page. Admin clicks the profile page button to view his/her profile. Profile page is opened.
2 Changing password. Admin types the old password, a new pssword, and retypes it. If all data is valid, s/he changes his/her password.
3 Filling personal information. Admin can enter his/her name and surname. His/her information is updated.
4 Updating profile photo. Admin selects a photo and clicks the update button. His/her profile photo is updated.

Test Case ID: EDIT_TEMPLATE

Test Priority: Moderate

Test Scenario: Admin wants to update an existing template.

Test Purpose: To test if the admin can successfully edit the template.

Designed by: Ebru Zorlu

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.3.1

Preconditions: Having an existing template and to be logged-in to the system.

Steps Test Steps Test Data Expected Data Actual Output
1 Editing a existing template. Admin clicks the edit(pen) button next to the existing template. A panel page is opened for modifying the template.
2 Typing and updating the template. S/he changes the template by typing a new one and adding new variables and actions. If modified fields are valid they are ready to save.
3 Saving the template edit page. S/he clicks save. The template is editted succesfully.

Test Case ID: DELETE_TEMPLATE

Test Priority: Moderate

Test Scenario: Admin wants to delete a template.

Test Purpose: To test if the admin can delete template of a node from conservation graph.

Designed by: Ebru Zorlu

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.3.1.2

Preconditions: Having an existing template and to be logged-in to the system.

Steps Test Steps Test Data Expected Data Actual Output
1 Deleting a template. Admin clicks the delete(cross) button next to an existing template. System opens a dialog and asks "Do you want to delete this template?"
2 Completing the delete operation. S/he clicks yes on confirmation dialog. The template is succesfully deleted.

Test Case ID: ADDING_NEW_NODE

Test Priority: Moderate

Test Scenario: Admin wants to add new node to conversation graph.

Test Purpose: To test if the nodes are added successfully to the conversation graph.

Designed by: Ali Goksu Ozkan

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.1.

Preconditions: Having a valid admin account and logging into the website with that account, viewing the conversation graph.

Steps Test Steps Test Data Expected Data Actual Output
1 Adding a node Admin clicks on add new node to some node as child node. Adding node page is opened.
2 Filling the node adding page. Admin writes the name of the node, creates templates, actions and replies of this node. If modified fields are valid they set as specified.
3 Saving the node adding page. Admin clicks on save button. The node is successfully added to conversation graph.

Test Case ID: EDIT_NODE

Test Priority: Moderate

Test Scenario: Admin wants to edit a node to conversation graph.

Test Purpose: To test if the admins can edit nodes on the conversation graph.

Designed by: Ali Goksu Ozkan

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.3.

Preconditions: Having a valid admin account and logging into the website with that account, viewing the conversation graph.

Steps Test Steps Test Data Expected Data Actual Output
1 Editing a node Admin clicks on edit the node which is wanted to be edited. Editing node page is opened.
2 Filling the node editing page. Admin modifies some or all the followings; the name of the node, templates, actions and replies of this node. After filling clicks on save button. If modified fields are valid they set as specified.
3 Saving the node editing page. Admin clicks on save button. The node is edited.

Test Case ID: DELETE_NODE

Test Priority: Moderate

Test Scenario: Admin wants to delete a node from conversation graph.

Test Purpose: To test if the admins can delete nodes from the conversation graph.

Designed by: Ali Goksu Ozkan

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.2.

Preconditions: Having a valid admin account and logging into the website with that account, viewing the conversation graph.

Steps Test Steps Test Data Expected Data Actual Output
1 Deleting a node Admin clicks on delete the node which is wanted to be deleted. A dialog opens and asks admin "Do you want to delete this node?".
2 Completing the deletion Admin clicks yes on confirmation dialog. The node is successfully deleted from the conversation graph.

Test Case ID: SEARCH_NODE

Test Priority: Moderate

Test Scenario: Admin wants to search a node from conversation graph.

Test Purpose: To test if the admins can search specific nodes from the conversation graph.

Designed by: Salih Sevgican

Design date: 08.05.2017

Executed by:

Execution date:

Related Requirements: 1.2.2.3.1.4.

Preconditions: Having a valid admin account and logging into the website with that account, viewing the conversation graph.

Steps Test Steps Test Data Expected Data Actual Output
1 Searching a node Admin writes the specifications of a node in to the search area A list of nodes which meet the specifications appears .
⚠️ **GitHub.com Fallback** ⚠️