Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) Frenzy Team 01 Name First Role Second Role Third Role Ashwin Hariharan Software Architect Prototyper Implementer Ankur Palav Software Architect Prototyper Implementer Arpan Badeka Prototyper UML Modeler Implementer Jheel Somaiya Project Manager Life Cycle Planner Implementer Rishabh Sharma Software Architect Operational Concept Engineer Implementer, Trainer Sailee Rane Requirements Engineer Feasibility Analyst Implementer, Tester Alan Kwan IIV&V N/A Tester 12/05/16

2 Version History Date Author Version Changes made Rationale 12/05/16 JS 1.1 Complete TPC Final submission ii

3 Table of Contents TEST PLAN AND CASES (TPC)... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... IV 1. Introduction Test Strategy and Preparation Hardware preparation Software preparation Requirements Test Identification Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Resources and schedule Resources Staffing and Training Needs Schedule iii

4 Table of Tables Table 1: Requirements Matrix... 7 Table 2: TC Check the sold out ribbon on items that are sold Table 3: TC Check the on sale ribbon on items that are on sale Table 4: TC Check the item details on the pop-up header Table 5: TC Check the shop similar button in shop popup Table 6: TC Check the display of tagged items in the shop popup Table 7: TC Check if all the clothing tags have an associated link to the items Table 8: TC Check the functionality of the Shop similar button in gallery tag Table 9: TC Check the functionality of the Buy button in gallery tag Table 10: TC Sold out flag set for items in the gallery tag Table 11: TC Check the correctness of the location of a clothing tag present in the gallery tag Table 12: TC Checks result(json) correctness of Sort Items Based on Most Popular Table 13: TC Checks result(json) correctness of Sort-Items based on Price(Low to High) Table 14: TC Checks result(json) correctness of Sort-Items based on Price (High to Low) Table 15: TC Checks result(json) correctness of Sort-Items based on New Arrivals Table 16: TC Check the Sort Button on-click expands and collapse Table 17: TC Check appropriate Article Details Table 18: TC Check Item Tag correctness Table 19: TC Check Image Tag buttons Table 20: TC Check articles saved by buyer Table 21: TC Check Images in Item Slider based on the Article and Author Detail Table 22: TC Similar Item Query Relevance Testing Table 23: TC Similar Item Visualization Check Table 24: TC Same Brand Query Relevance Check... 33

5 Table of Contents Table 25: TC Empty Query Result check Table 26: TC Image URL does not exist Table 27: Testing Schedule v

6 1. Introduction This document mainly focuses on describing test cases and the acceptance criteria from win-win conditions documented in winbook. Our team tested the Frenzy web application from different levels, such as system testing, integration testing, unit levels and acceptance testing. Our team used Unit Testing for testing functionalities like Clothing Tag functionality, Sorting functionalities in the Shop Widget and Shop Similar modules. We also used Integration Testing for the Shop Popup and Article detail functionalities 6

7 2. Test Strategy and Preparation We built a series of test cases including sunny and rainy day scenarios based on the key functionalities for our system. We referred to the requirements in the winbook and make sure every requirement was included in our system. We are planning to use manual testing methods to test the performance of the Frenzy web application. 2.1 Hardware preparation We will need a computer with Ubuntu as the OS. The computer is capable of running Apache and MySQL server. AWS is used to for hosting the application. We also need regular computer or laptops having internet access for development of the application as well as testing. 2.2 Software preparation We need AngularJS for Front end development, Codeigniter for backend development, and Linux on a computer for running testing cases 2.3 Requirements Table 1: Requirements Matrix Requirement ID Verification Test Case ID (if applicable) Type CR-1 Shop Widget Testing TC-01: Browsing through the shop popup in the shop widget TC Check the sold out ribbon on items that are sold. TC Check the on sale ribbon on items that are on sale. TC Check the item details on the pop-up header. TC Check the shop similar button in shop popup. TC Check the display of tagged items in shop popup 7

8 CR-2 Clothing Tag Testing TC-02: Clothing Tag functionality TC The concentric tags present in the articles will be checked to provide a valid link to the related item. Null clothing tags will also be detected by the test case in order to remove them from the system. TC Check the functionality of the Shop similar button in gallery tag TC Check the functionality of the Buy button in gallery tag TC Sold out flag set for items in the gallery tag TC Check the correctness of the location of a clothing tag present in the gallery tag CR-3 Sorting Functionality CR-4 Article Detail Functionality CR-5 Similar Items Functionality Testing TC-03: Sort-Items Functionality in Shop Widget based on Popularity, Price and New Arrival. TC Checks result(json) correctness of Sort Items Based on Most Popular TC Checks result(json) correctness of Sort-Items based on Price(Low to High) TC Checks result(json) correctness of Sort-Items based on Price(High to Low) TC Checks result(json) correctness of Sort-Items based on New Arrivals TC Check the Sort Button on-click expands and collapse Testing TC-04 Article Detail Functionality TC Check appropriate Article Details TC Check Item Tag correctness TC Check Image Tag buttons TC Check articles saved by buyer TC Check Images in Item Slider based on the Article and Author Detail Testing TC-05: Similar Items Functionality TC Similar Item Query Relevance Testing TC Similar Item Visualization Check TC Same Brand Query Relevance Check TC Empty Query Result check TC Image URL does not exist 8

9 3. Test Identification 3.1 Test Identifier TC-01: Browsing through the shop popup in the shop widget Test Level Integration testing level Test Class Erroneous input testing & timing testing Test Completion Criteria List of completion criteria:- a. The shop popup displays only the tagged items in the grid once shop button is clicked. b. Each of the items, display details like brand, title & price upon hovering on them & the center item displays it by default on load. c. The sold out items are appropriately labeled with a sold out ribbon across them. d. The items on sale are appropriately labeled with an on sale ribbon across them. e. Each of the items has a shop similar button below them Test Cases TC Check the sold out ribbon on items that are sold. TC Check the on sale ribbon on items that are on sale. TC Check the item details on the pop-up header. TC Check the shop similar button in shop popup. TC Check the display of tagged items in shop popup 9

10 Table 2: TC Check the sold out ribbon on items that are sold. Expected Output Specifications Pass/Fail Criteria TC Check the sold out ribbon on items that are sold. This test case will test the sold out functionality of the module by providing it with 0 & 1 values from the backend. This is a must have functionality as it helps the user in decision making. The user should be in the shop widget section and must have clicked the shop button. The user either scrolls for other items or closes the widget. Flags of 0 & 1 are set in the backend table and accordingly the output is checked. The item out of stock is displayed with a sold out ribbon across it. Pass if item with flag of 0 has a ribbon. Pass if item with flag of 1 has no ribbon. Fail if item with flag of 0 has no ribbon. Fail if item with flag of 1 has a ribbon. Fail if the loader animation keeps displaying without showing any ribbons for appropriate items. Assumptions and Constraints Fail if the ribbons are shown/not shown for flag values apart from 0 or 1. No assumptions. This test case can be executed independently. Shop Widget: WC_

11 Table 3: TC Check the on sale ribbon on items that are on sale. Expected Output Specifications Pass/Fail Criteria TC Check the on sale ribbon on items that are on sale. This test case will test the on sale functionality of the module by providing it with 0 & 1 values from the backend. This is a must have functionality as it helps the user in decision making. The user should be in the shop widget section and must have clicked the shop button. The user either scrolls for other items or buys the on sale item. Flags of 0 & 1 are set in the backend table and accordingly the output is checked. The item on sale is displayed with an on sale ribbon across it. Pass if item with flag of 0 has no ribbon. Pass if item with flag of 1 has a ribbon. Fail if item with flag of 0 has a ribbon. Fail if item with flag of 1 has no ribbon. Fail if the loader animation keeps displaying without showing any ribbons for appropriate items. Assumptions and Constraints Fail if the ribbons are shown/not shown for flag values apart from 0 or 1. No assumptions. This test case can be executed independently. Shop Widget: WC_

12 Table 4: TC Check the item details on the pop-up header Expected Output Specifications Pass/Fail Criteria TC Check the item details on the popup header. This test case will test the item details in the pop-up header when the shop button is clicked or when the item is hovered on. This is a must have functionality as it helps the user in decision making. The user should be in the shop widget section and must have clicked the shop button. The user either scrolls for other items or buys one of the items. Providing item details from the backend. The center image has its details displayed by default and on hovering on other items it displays the corresponding details on their respective headers. Pass if the center item displays its details by default. Pass if the non-centered items display their details on their headers upon hovering on them. Fail if the center item doesn t display its details by default. Fail if the other items don t display their details upon hovering on them. Assumptions and Constraints Fail if the loader animation keeps displaying without showing any item details. No assumptions. This test case can be executed independently. Shop Widget: WC_

13 Table 5: TC Check the shop similar button in shop popup. Expected Output Specifications Pass/Fail Criteria TC Check the shop similar button in shop popup. This test case will test the shop similar button when there are 0> items to display & when there are 0 items to display. This is a must have functionality as it helps the user to shop similar products. The user should be in the shop widget section and must have clicked the shop button. The user either scrolls for other items or clicks the shop similar button for similar products. From the backend we provide either 0 items or more than 0 items. Each item is displayed with a shop similar button below it. Pass if each item has a shop similar button below it. Fail if items are displayed with no shop similar button. Assumptions and Constraints Fail if shop similar buttons are displayed when there are no items to display. No assumptions. This test case can be executed independently. Clothing Tags: WC_

14 Table 6: TC Check the display of tagged items in the shop popup. Expected Output Specifications Pass/Fail Criteria TC Check the display of tagged items in the shop popup. This test case will test the items in the grid when there are no items tagged & when there are multiple items tagged. This is a must have functionality as without it the user would not be able to shop. The user should be in the shop widget section and must have clicked the shop button. The user either scrolls for other items or buys one. In the backend we store (tag) items in images and pass these values to the front end. All the tagged items are displayed in the shop popup grid. Pass if the tagged items are displayed in the shop popup grid. Assumptions and Constraints Fail if the tagged items are not displayed in the grid. Fail if the items are displayed when there are no items tagged in the image. Fail if the loader animation keeps displaying without showing any items. No assumptions. This test case can be executed independently. Shop Widget: WC_

15 3.2 Test Identifier TC-02: Clothing Tag functionality Test Level Unit Testing Test Class Erroneous Input Testing Test Completion Criteria This test will be completed when: They evaluate the clothing tags for its appropriate locations and item details in the article runway tab The options provided for user in the gallery tags like the buy, save and shop similar buttons need to work according to their specified functionality The test cases should complete the checks for these functionalities of the clothing tags to help improve the web application Test Cases TC-02: Clothing Tag functionality TC The concentric tags present in the articles will be checked to provide a valid link to the related item. Null clothing tags will also be detected by the test case in order to remove them from the system. TC Check the functionality of the Shop similar button in gallery tag TC Check the functionality of the Buy button in gallery tag TC Sold out flag set for items in the gallery tag TC Check the correctness of the location of a clothing tag present in the gallery tag 15

16 Table 7: TC Check if all the clothing tags have an associated link to the items. TC Check if all the clothing tags have an associated link to the items. The concentric tags present in the articles will be checked to provide a valid link to the related item. Null clothing tags will also be detected by the test case in order to remove them from the system. Must have Before running the test case on any article, the presence of clothing tags must be checked. In the absence of a tag, disregard that article for the test case The test case should return a valid link for the tagged article. Article Name, Author Name, Tab (Runway article/article detail) Expected output specifications Pass/fail Criteria Assumptions and constraints Item clothing detail, Item price, item image, item brand and item category Pass criteria- Valid item details Fail criteria- Wrong item detail and category, null item links The articles should be linked. TC Check the correctness of the location of a clothing tag present in the gallery tag As a user I can check the item details by clicking on the clothing tag. Table 8: TC Check the functionality of the Shop similar button in gallery tag TC Check the functionality of the Shop similar button in gallery tag The shop similar button present in the pop up window (gallery tag) when clicked, redirects user to the similar items shop widget Must Have The shop similar button must have the functionality to query the database to return similar items when clicked. 16

17 The items returned must be displayed in the shop similar widget, where at the most three items are viewed at a time Item detail, item brand, category and price Expected output specifications Pass/fail Criteria Assumptions and constraints Items with similar category (default). Default items are displayed when similar items are not present in the database. Pass Criteria- Similar product items are returned when shop similar button is clicked e.g. Shop similar button for bags will return the articles containing bags Similar items are present in the database. TC Check if the clothing tags have an associated link to the items (which are displayed in gallery tags) As a user, I should be able to see similar items when shop similar button is clicked. Table 9: TC Check the functionality of the Buy button in gallery tag TC Check the functionality of the Buy button in gallery tag The buy button in the pop up window must redirect the user to the retailer s website. Must have The buy button must have the functionality to query the database to find the retailer s website. The user should be redirected to the retailer s website when the buy button is clicked. Item brand, detail, category and price, sold out flag (0/1) Expected output specifications Pass/fail Criteria Link to the retailer s website for the item whose buy button is clicked in the pop up window or greyed out button for sold out items Pass Criteria- Valid retailer link for the item being queried. Greyed out buy button when the item is sold out 17

18 Fail Criteria- Invalid retailer s website when buy button is clicked Assumptions and constraints The database contains the information of the retailer s website to buy items after clicking on the shop similar button. TC Check if all the clothing tags have an associated link of the items. As a user, I should be directed to the retailer s website when the buy button is clicked. Table 10: TC Sold out flag set for items in the gallery tag TC Sold out flag set for items in the gallery tag The gallery tag item window should have sold out ribbon if the item is not present on the retailer website Should Have The clothing tag being accessed must have flag set in the database to indicate if the item is sold out The item in the gallery tag should have a sold out ribbon. Item detail, brand, category and price Expected output specifications Sold out ribbon on items whose flags are set. Pass/fail Criteria Assumptions and constraints Pass criteria- Sold out ribbon on flagged items Fail criteria- No ribbons are set on items which are flagged Assumption-The database contains an up to date information of all the sold out items and maintains a flag to reflect this information. TC Check if all the clothing tags have an associated link of the items. As a user, I can see the sold out items when I click on the clothing tags. 18

19 Table 11: TC Check the correctness of the location of a clothing tag present in the gallery tag TC Check the correctness of the location of a clothing tag present in the gallery tag The article image should have the clothing tags on the appropriate items and not on void fields Must have The clothing tags location on the image should be retrieved from the database The clothing tags should appear on appropriate locations of the article detail Article image, tag location and item detail Expected output specifications Clothing tag set on proper locations in the article detail Pass/fail Criteria Assumptions and constraints Pass criteria- related clothing tag displayed on the article Fail criteria- clothing tags set on null fields The database contains the information of the clothing tag location in the article detail. None -As the clothing tags are set by the client -developers for the existing Frenzy system. As a user, I should see the clothing tags on article images to see more information 3.3 Test Identifier TC-03 Sort-Items Functionality in Shop Widget based on Popularity, Price and New Arrival Test Level Unit testing 19

20 3.3.2 Test Class Erroneous input testing Test Completion Criteria The list of completion criteria specific for this test identifiers are: i. All the modules associated with the Sort-Item Functionality of Shop Widget must give results accurately and efficiently. ii. The Most Popular module must return all the popular items in correct order based on the popularity (maximum sold items in descending order). iii. The Price (Low to High) module must return all the items in ascending order based on the Price of the items present in Shop Widget. iv. The Price (High to Low) module must return all the items in descending order based on the Price of the items present in Shop Widget. v. The New Arrivals module must return all the items based on timestamp attached with them (ordering the items, providing latest items first). vi. The Sort-Item Popup must open when user clicks on the sort button and collapse when user click anywhere outside the popup or again on the button or select any of the above module. If all the above criterions for the test identifier are fulfilled and they work as required, then testing is complete Test Cases TC Checks result(json) correctness of Sort Items Based on Most Popular TC Checks result(json) correctness of Sort-Items based on Price(Low to High) TC Checks result(json) correctness of Sort-Items based on Price(High to Low) TC Checks result(json) correctness of Sort-Items based on New Arrivals TC Check the Sort Button on-click expands and collapse Table 12: TC Checks result(json) correctness of Sort Items Based on Most Popular. TC Checks result(json) correctness of Sort Items Based on Most Popular. Most Popular functionality of Sort-Items is the test item and basically, it allows user to sort the items based on the popularity. And the algorithm which implements this based on popularity, uses the maximum sold item count as reference to provide the results. 20

21 Expected Specifications Output As we are using using select query to fetch item count from item-sold count column and return JSON. So the following features our test case will cover: i. It will check if some items in the column has big value associated with it and then append those items to JSON. ii. If the count column consists of NULL value, the test case will handle the NULL check condition and return an appropriate JSON result. iii. It will also check the results provided in the JSON are in sorted format based on the algorithm, that is, will check the algorithm working efficiently or not. M(Must Have): As it is also an type of e-commerce website, and sorting items based on popularity is one of the most essential thing which most of the users look for in a website before buying a item. The Most popular function exists inside the shop widget, therefore, the shop widget class must be executed in order to execute Most Popular functionality. On running the test case on the Most Popular function, it must generate a JSON consisting of item details sorted in decreasing order based on popularity(maximum sold items count). To check all the Most Popular functionality, since count is the input based on which results are fetched. Therefore, following input conditions are required to be tested: i. If the input count associated with all the elements is made NULL, then does it is handling the condition. ii. If value assigned to count for some element is very big, and rest is very low, then does it handle the condition. iii. The random count is assigned to the items, then does it give proper JSON based on popularity. The expected output specifications are: i. When all the count values are NULL, then it must retain the JSON before sort operation performed. ii. When few items have very big count value, then it must generate the JSON having only the value near to that big value, to maintain the consistency. iii. The JSON output generated must contain details of all the items and the list of the items must be in descending order based on the popularity. Pass/Fail Criteria Assumptions and Constraints Pass Criteria: When the JSON generated are appropriate based on the input of the count. If all the counts are NULL, then it must retain the JSON. If some counts have very big value, then it must give only the JSON having items near to that big value. If all counts are having some random value, then it must generate a JSON having items based on popularity in decreasing order. Fail Criteria: When the JSON generated does not contain items in descending order based on popularity. If the JSON is not retaining itself when count value is NULL. If the JSON generated also contains with low count in comparison to the elements containing count very high. The database tables must have all the required details and entity relationship. This is an independent test case. WC_4237: As a user, I can sort the products by it's popularity (Maximum number of items sold) so that I can get the best available 21

22 product. Table 13: TC Checks result(json) correctness of Sort-Items based on Price(Low to High) Expected Specifications Pass/Fail Criteria Output TC Checks result(json) correctness of Sort-Items based on Price(Low to High) Price (Low to High) Functionality of Sort-Items is test item, as it allows the user to sort the items based on the Price, returning low price elements first. The Algorithm used to return the JSON of the elements according to price, uses the Price column attached with the item and returns a JSON result with Price in increasing order. As we are using the select query to fetch the data from the database based on the price and sorting the data in ascending order based on price and returns JSON. Therefore, following features our test cases will cover: i. It will check if the JSON generated after querying is in sorted format based on the price (Low to High). ii. It will check that with the price column, and if items have NULL values, then test case will have handle NULL check condition and return an appropriate JSON result. iii. It will check that appropriate JSON result is returned, even when all prices are same. M (Must Have): As the website will provide ease to users looking for branded products for less price. This sort will unable those users to look the cheap options available. The Price (Low to High) function exists inside the shop widget, therefore, the shop widget class must be executed in order to execute Price (Low to High) function s functionality. On running the test case on the Price (Low to High) function, it must generate a JSON consisting of item details sorted in ascending order based on Price Column in Database. To test all the Price (Low to High) Functionality, the input given is the price of the item based on which results are obtained. Therefore, following input conditions are required to be tested: i. If all the items have same price, then it must handle the condition. ii. If all the items have NULL price associated with them, it must handle the condition. iii. If prices are assigned to each item, thenthe JSON generated must contain items in ascending order based on price. The expected output specifications are: i. If all the items have same price, then it must retain the JSON before sort operation performed. ii. If all the items have NULL price associated with them, then also it must retain the JSON before sort operation performed. iii. If all the prices exists and in proper format, the resulted JSON must contain the list of items in ascending order based on the Price (Low to High). Pass Criteria: If the JSON result generated is in the proper ascending order based on price (low to high). If it retains the JSON file which was previous to sort operation when all prices are NULL or all prices are same and price (low to high) functionality if performed. 22

23 Assumptions and Constraints Fail Criteria: If the JSON result generated is not in proper ascending order based on price (low to high). If it is not able to retain the JSON before the sort operation is performed, when all the prices are NULL or all prices are same. The database tables must have all the required details and entity relationship. This is an independent test case. WC_4236: As a user, I can sort the products by it's price (low to high and high to low) so that I can get the product of my price range easily. Table 14: TC Checks result(json) correctness of Sort-Items based on Price (High to Low) TC Checks result(json) correctness of Sort-Items based on Price (High to Low) Price (High to Low) Functionality of Sort-Items is test item, allows the user to sort the items based on Price, returning item with highest value first, followed by lower than previous value and so on. The algorithm implemented to sort the items based on price, sends a request to the database and fetches all the Price items and order them in descending order based on price. As we are using the select query to fetch the data from the database based on the price and sorting the data in descending order based on price and returns items JSON. Therefore, following features our test cases will cover: i. It will check if the JSON generated after querying is in proper sorted format based on the price (High to Low). ii. It will check that with the price column, and if items have NULL values, then test case will have handle NULL check condition and return an appropriate JSON result. iii. It will check that appropriate JSON result is returned, even when all prices are same. M (Must Have): As our website is an e-commerce website and it cover wide range of users, which include rich buyers, who consider quality over price. They look for expensive products, thus requires sorting items based on Price (High to Low). The Price (High to Low) function exists inside the shop widget, therefore, the shop widget class must be executed in order to execute Price (High to Low) function s functionality. On running the test case on the Price (High to Low) function, it must generate a JSON consisting of item details sorted in descending order based on Price Column in Database. To test all the Price (High to Low) Functionality, the input given is the price of the item based on which results are obtained. Therefore, following input conditions are required to be tested: i. If all the items have same price, then it must handle the condition. ii. If all the items have NULL price associated with them, it must handle the condition. iii. If prices are assigned to each item, then the JSON generated must contain items in descending order based on price. Expected Output The expected output specifications are: 23

24 Specifications i. If all the items have same price, then it must retain the JSON before sort operation performed. ii. If all the items have NULL price associated with them, then also it must retain the JSON before sort operation performed. iii. If all the prices exists and in proper format, the resulted JSON must contain the list of items in descending order based on the Price (High to Low). Pass/Fail Criteria Pass Criteria: If the JSON result listed items in a descending order based on Price (High to Low). If all the items have same price, then it must retain the JSON before sort operation performed. If all the items have NULL price associated with them, then it must retain the JSON before the sort performed. Fail Criteria: If the JSON result listed items are not in a proper format as required. If all items have NULL price associated or all prices are equal but JSON can t be retained to the one which was before the sort functionality was performed. Assumptions and Constraints The database tables must have all the required details and entity relationship. This is an independent test case. WC_4236: As a user, I can sort the products by it's price (low to high and high to low) so that I can get the product of my price range easily. Table 15: TC Checks result(json) correctness of Sort-Items based on New Arrivals TC Checks result(json) correctness of Sort-Items based on New Arrivals New Arrival Functionality is test item, allows the user to sort the items based on the current date-time minus creation date-time in ascending order. Thus, returning the list of items in ascending order of the value obtained by subtracting current date-time to creating datetime. As we are using select query to fetch data from the database based on creation date-time and sorting it based on the subtraction of current date-time to creation date-time and returns items JSON. The following features our test-case will cover: i. It will check the JSON generated after running the query based on the creation date-time, and sorting it based on difference of current date-time and creation date-time and ordering it in ascending order. ii. It will check for the results shown should be limited to 7 days, by putting a threshold of 7 on the difference of current date-time and creation date-time. M (Must Have): As many users want to see the latest fashion products present on website or in blog. Therefore, New Arrival option allows them to sort the items based on creation time. The New Arrival function exists inside the shop widget, therefore, the shop widget class must be executed in order to execute New Arrival function s functionality. On running the test case on the New Arrival function, it must generate 24

25 a JSON consisting of item details sorted in ascending order based on the difference of current date-time and creation date-time and limiting it to 7 days. To test all the New Arrival Functionality, the input given is the creation time of the item and current date-time based on which results are obtained. Therefore, following input conditions are required to be tested: i. If creation date-time is the input, then it must generate appropriate output of according to the current date-time and create date-time. Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints The expected output specifications is: The JSON obtained based on the input must be listing items in ascending order based on difference of current date-time and creation date-time and limiting the results to 7 days. Pass Criteria: If the JSON generated is in proper format and limited to 7 days. Fail Criteria: If the JSON generated is not in appropriate order and not limited to 7 days. The database tables must have all the required details and entity relationship. This is an independent test case. WC_4234: As a user, I can sort the products by creation time, so that I can possibly follow the latest trends. Table 16: TC Check the Sort Button on-click expands and collapse TC Check the Sort Button on-click expands and collapse On-click Sort Button expands and collapse is the test item, allows the user to select the sort button providing the list of sorting functions. It must expand when the user clicks on it and must collapse when user again click on it or anywhere in the shop widget or when user selects any of the sort menu item. The features our test cases will cover: i. If the user clicks on the button, the menu must expand. ii. If the user clicks on the button again, the menu must collapse. iii. If the user selects any of the menu function, the menu must collapse and the shop widget must display results. iv. If the user clicks anywhere on the shop widget when the menu drop down is on, then it must collapse. M (Must Have): As interaction with the platform attracts more users. Smoother the interaction, better the user experience. Therefore, this expand and collapse feature allows user to view only the essential elements in shop widget and sort drop down is not visible until user clicks on it. Making the UI clean and having more functionality. The expand and collapse function exists inside the shop widget, therefore, the shop widget class must be executed in order to execute this functionality. The Sort Drop Down menu either in expanded state or collapsed state based on the operation performed. If the user clicks on the button first 25

26 Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints time, it will expand. If the user clicks on the second time, it will collapse or anywhere on the shop widget it will collapse or select any function from the drop down menu it will collapse. The on mouse click is the input for Sort Drop Down menu expand and collapse functionality. The following output specifications needed: i. On mouse click input on the button, expand() function in JavaScript must be called. ii. On mouse click input on button second time in the shop widget, collapse() function must be called. iii. On mouse click input anywhere in shop widget, collapse() function must be called in the shop widget JS function. iv. On mouse click on any of the function in sort drop down menu, must call collapse() function inside the function selected from the drop down, such that it collapses the drop down as soon as any of the function is selected. Pass Criteria: If the user clicks the first time, it must expand. If the user clicks the second time it must collapse. If the user clicks anywhere in shop widget and drop down is open then it must collapse. If the user clicks on any of the function in sort menu, then it must collapse. Fail Criteria: If the menu doesn t open on click. If the menu doesn t collapse when user double clicks on it or somewhere on the shop widget. If the menu does not collapse when user selects any of the sort function present in its drop down menu. Assumed that all the sort functions inside the Sort Drop Down Menu work completely fine without any bug. It is dependent on the above four test cases: T-03-01, T-03-02, T-03-03, T As collapse function is called inside there JS Function. WC_4233 As a user, I can collapse the "sort by drop down menu box" by clicking anywhere on the page except the box for better user experience. 3.4 Test Identifier TC-04: Article Detail Functionality Test Level Integration testing 26

27 3.4.2 Test Class Erroneous input testing Test Completion Criteria The Article Detail Test Cases are considered completed if the correct article detail is displayed when: -The buyer views the entire article information, -The Item details displayed are relevant to the Item in the Article, -The buyer can view options like save, buy and shop similar items, -The buyer can view items he saved for future use -The shop widget displays other items belonging to the same author Test Cases TC Check appropriate Article Details TC Check Item Tag correctness TC Check Image Tag buttons TC Check articles saved by buyer TC Check Images in Item Slider based on the Article and Author Detail Table 17: TC Check appropriate Article Details TC Check appropriate Article Details The suitable Article Details will be checked when the buyer wishes to see the article explanation Must have Buyer must have access to view the entire article description page. All the information from the Runway Article page must be displayed in the Article Detail page Proper article details with the correct item specifications and tags Article ID, Author Name, Article Name, Item ID Expected output specifications Article Name, Article Content, Style Tag, Item Tag, Item Image Pass/fail Criteria Pass criteria: The required article information is displayed Fail Criteria: Article information not relevant to the article being viewed 27

28 Assumptions and constraints The article must be present in the database in order to display the relevant information TC-02-01: To check if clothing tags display the corresponding item details in a article As a user I can see the article details by clicking on Read Full Article Table 18: TC Check Item Tag correctness TC Check Item Tag correctness The Item details on the Article Detail page will be checked when the buyer clicks on the image popup Must Have Buyer must have access to view the entire article description page. All the Item tags should be visible to the buyer when he hovers over the article image Item information relevant to the item being viewed in the article Article ID, Author Name, Article Name, Item ID Expected output specifications Item ID, Item name, Item price, item image, Brand, Specifications Pass/fail Criteria Assumptions and constraints Pass criteria: The required item detail being displayed within the article Fail Criteria: Item information not relevant to the item being viewed by the buyer in the article and the item has some missing parameters The article must be present in the database in order to display the relevant information. The items in the article must be tagged TC-04-01: To check if relevant Article Detail of an article is displayed As a user I can see a particular Item Detail within an article 28

29 Table 19: TC Check Image Tag buttons TC Check Image Tag buttons The buttons on the gallery tag popup will be checked when the buyer hovers over the Item Tag Must Have Buyer must have access to view the entire article description page. All the Item tags should be visible to the buyer when he hovers over the article image Buttons displayed should be relevant with the actions that can be performed when the buyer views the gallery tag Item ID, Item detail, item name, item brand and price Expected output specifications Save, Buy, Similar buttons for gallery tags Pass/fail Criteria Assumptions and constraints Pass criteria: The required action buttons are displayed to the buyer Fail Criteria: Buttons are not displayed to the buyer in the gallery tag The article must be present in the database in order to display the relevant information. The items in the article must be tagged TC-04-02: To check if Item details are displayed correctly in the Item Tags As a user I have the option to save, buy and view similar items Table 20: TC Check articles saved by buyer TC Check articles saved by buyer Article will be marked as saved if the user wishes to come back later and buy the item from an article Should Have Buyer must have access to view the entire article description page. A save button should be visible to the buyer to Save the article 29

30 The item must be marked as saved if the user wants to save it Article ID, Item brand, name, detail and price Expected output specifications Pass/fail Criteria Assumptions and constraints Article marked as Save. User profile shows the article in the Saved Article section Pass criteria: The article is saved to the user profile page and is marked as Saved only if the user logs in and clicks on Save Fail Criteria: The article does not appear in the Saved Article Section even if the User has logged in and saved it Buyer must have a valid user account on Frenzy.me. The article must be present in the database in order to display the relevant information. The items in the article must be tagged with the respective buttons TC-04-03: To check if the user has an option to save the article As a user I have the option to view my saved articles Table 21: TC Check Images in Item Slider based on the Article and Author Detail TC Check Images in Item Slider based on the Article and Author Detail The Shop Widget should display other items belonging to the same author, if any Should Have Buyer should have access to view the entire article description page Shop Widget should have other Items that belong to the same Author, if they exist Article ID, Author Name 30

31 Expected output specifications Pass/fail Criteria Assumptions and constraints Article ID, Author Name, Item ID and images of other items belonging to the same author Pass criteria: The items that belong to the same author are displayed in the shop widget with the option to buy those items as well, if available Fail Criteria: There are no items displayed in the shop slider even if the author has other items The article must be present in the database with an author name in order to display the relevant article and author information TC-04-01: To check if relevant Article Detail of an article is displayed As a user I have the option to view other items that belong to the same author 3.5 Test Identifier TC-05: Similar Items Functionality Test Level Unit Testing Test Class Erroneous input testing and stress testing Test Completion Criteria The following criteria needs to be considered: - 1) Query result is accurately generated depending on the input ItemGuID 2) Visualization of Query result (mapping between item ImageIds, title, name, price, brand, color, relevant flags are precise.) Test Cases TC Similar Item Query Relevance Testing TC Similar Item Visualization Check 31

32 TC Same Brand Query Relevance Check TC Empty Query Result check TC Image URL does not exist Table 22: TC Similar Item Query Relevance Testing Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints TC Similar Item Query Relevance Testing Check for relevance of queries when user clicks on similar items (Click on purse should yield purses of roundabout the same color) M ItemGuiD of the product selected exists in the Items table in the database The tables Item, ItemDetails should have ItemGuIDs of the same category (as the product whose similar items is clicked). Data is not sparse to output no result in which case we won t be able to test the relevance The list of items generated must have the same category and the colorid as the item who similar item is clicked Input is the ItemGuID whose similar item checkbox is clicked A list of Item details array, each having same category Id and Color Id as the clicked item Passes if all selected items have same category Id and color Id as the selected product and at the same time the array visual is similar as well. Fails if that s not the case. Assuming that appropriate colorids and category Ids fields are set in the ItemDetails, Items table. Assuming that the data is not sparse and selects at least one item of each category. WC_4238 As a user, I can view a cluster of similar products for each selected product Table 23: TC Similar Item Visualization Check TC Similar Item Visualization Check Check if the image array mapping, item details (price, brand, title) visualization is accurate. M The similar items query generates a JSON and dispatches it to the frontend (with or without 32

33 Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints modifications (to be tested)) for visualization The Item details JSON visualized in the front end must have accurate mappings to item image array, and appropriate listings of price, brand, title against each product element inside the shop widget product slider. Input is a JSON (Query Result) that generated by the similar items query A collection of item details array displaying desired product images, titles, price, brand for each product element under scrutiny as reflected in the JSON. Passes if the visualization of item details in the shop widget is in terms with the fetched JSON. Fails if that s not the case. Assuming that the fetched JSON from similar items is accurate and has all the mappings to be tested. Also a constraint that no mapping inside JSON and/or JSON object is null TC WC_4238 As a user, I can view a cluster of similar products for each selected product Table 24: TC Same Brand Query Relevance Check Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints TC Same Brand Query Relevance Check Check if the same brand query fired yields relevant same brand products M All items in the ItemsDetail and Items table are attached correctly to the brands JSON generated from the similar brand query must have all the product elements having the same brand Input is the ItemGuID of item whose same brand is clicked A JSON composed of array of ItemGuIDs each mapping to a tuple that has brand field same as the brand of the input ItemGuID Passes if the JSON is validated for each product element that is for all product elements in JSON, brand is same as the brand of the selected product Assuming that brand field is set in the database 33

34 table ItemsDetail WC_4238 As a user, I can view a cluster of similar products for each selected product Table 25: TC Empty Query Result check Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints TC Empty Query Result check Check if the empty/null query result does not break the shop widget functionality M User clicks on similar items or same brand checkbox There should exist items with unique brand, color id, category fields values in Item, ItemDetails and ItemSearch tables of the database Empty query result must be generated and dispatched to the frontend and front end shows the appropriate message Input is ItemGuiD that has a unique brand value, category or color An empty JSON object which is defined so that accessing it won t result in null pointer exception. Passes if an empty query result is returned and visualization is an appropriate message. User has clicked the product elements in one of the following tabs :- popular, spring campaigns or Asian Street Style WC_4238 As a user, I can view a cluster of similar products for each selected product Table 26: TC Image URL does not exist TC Image URL does not exist Check if null or incorrect image URLS M User clicks on similar items or same brand checkbox If the image URL source is not found or does not exist, default image thumbnail must be displayed to the user. Input is ItemGuiD for which similar item/ same brand query is to be fired 34

35 Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints A list of product elements where, for all products elements, a default image is displayed if the image url source is not found or does not exist and appropriate image url image is shown otherwise. Passes if default image url is displayed in case of image url source not found/does not exist, and shows a valid image in case of valid image source. Fails otherwise. User has clicked the product elements in one of the following tabs: - popular, spring campaigns or Asian Street Style The query result contains the array of image url for each product element. TC-05-01, TC WC_4238 As a user, I can view a cluster of similar products for each selected product 35