@zqaderi.sire thanks for submitting your assignment.

@Redwan Dergeba thanks for submitting your assignment.

New Test Case -10 Regression Test cases-5

NEW TEST CASES -10 case Regression Test Cases- 5 test cases

zqaderi.sire, the person who always submit the assignment first. I thought you will create a new thread and we will post our assignment there but as you posted your assignment under last weeks thread that's why we followed you and post our assignment here.

@Redwan Dergeba Thanks for your feedback.

New Test cases- 10 test cases Regression Testing-5 test cases

@Redwan Dergeba thanks for you feedback. My task was to test or verify different columns or buttons under the same URL which i mentioned in test scenario section "Testing Functionality of Shop Microsoft Surface family products under Best Buy page". In my test case steps my 1st step was "open www.bestbuy.com and then i moved to next steps. It seems to me a wise idea to complete my different tasks staying in the same URL rather leaving the page after one task and start from the 1st step again and again.

Dynamic Testing: Dynamic testing technique is the type of testing that validates the functionality of an application when the code is executed. In simple terms dynamic testing is performed by using the application and seeing if a functionality works the way it is expected to. What does dynamic testing do? The main aim of the Dynamic tests is to ensure that software works properly during and after the installation of the software. The main purpose of the dynamic test is to ensure consistency to the software. Consistency is not only limited to the functionality it also refers to different standards like performance, usability, compatibility etc. Different types of Dynamic testing with my project adding 'Vegetable column in Subway' described below: Dynamic Testing is classified into two categories White Box Testing The method of White Box testing is to check on how System is performing based on the code. It is mainly performed by the Developers or White Box Testers who has knowledge on the programming. Black Box Testing Black box testing is a method of testing to verify the functionality of the system under test and this type of testing requires to execute the complete test suite and is mainly performed by the Testers. Black Box Testing classified in 2 types Functional Testing and Non-Functional Testing Functional Testing: As the name itself suggests, this is the type of testing that validates the functionality of the application. Functional Testing is performed to verify that all the features developed are according to the functional specifications, and it is performed by executing the functional test cases written by the QA team, in functional testing phase, system is tested by providing input, verifying the output and comparing the actual results with the expected results. There are different Levels of Functional Testing out of which the most important are: UNIT TESTING: Is a type of software testing where individual units or components of a software are tested. The purpose is to validate that each unit of the software code performs as expected. Unit Testing is done during the development (coding phase) of an application by the developers. For my project add vegan and vegetarian column in Subway.com, developer will test different component during coding phase to confirm the vegetarian column will perform as per requirement. INTEGRATION TESTING: Is the testing which is performed after Unit Testing and is performed by combining all the individual units which are testable and is performed either by developers or testers. For my project developer will test the units and the combination like when customer will click on Vegetarian button it will directed to a new page with all vegan items with details. SYSTEM TESTING: Is a level of software testing where a complete and integrated software is tested. The process of testing an integrated system to verify that it meets specified requirements. At this stage developer complete the coding for add vegetarian column in subway page and software is ready for the QA team to test the performance of the ‘Vegetarian column’ according to the requirement. ACCEPTANCE TESTING: is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment. In a separate testing environment two or three end user will use the subway web page to find the vegetarian column and could use the all functionality like all vegetable items with picture, health benefits, price and other features if included in the requirement. NON-FUNCTIONAL TESTING: is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application. There are different Levels of Non-Functional Testing out of which the most important are: Performance Testing: Checks the speed, response time, reliability, resource usage, scalability of a software program under their expected workload. In Subway web page customers can access Vegetarian Column fast and a lot of customers can browse the page at a time and able to find the vegetable items with details in that column. Recovery Testing: Is a method to verify on how well a system can recover from crashes and hardware failures. It is done by professional testers. Before recovery testing, adequate backup data is kept in secure locations. This is done to ensure that the operation can be continued even after a disaster. If Subway web page is difficult to access reloading the browser help to enter the web page. Compatibility Testing: Is performed to verify how the system behaves across different environments. Subway web page can accessible from different environment like Explorer, Chrome and mobile device. Security Testing: Is performed to verify the robustness of the application which ensure that only the authorizes users/roles are accessing the system. Subway ensure customers security which assure customers to pay online using their bank cards.

SOAP stands for Simple Object Access Protocol. SOAP is a protocol which was designed before REST and came into the picture. The main idea behind designing SOAP was to ensure that programs built on different platforms and programming languages could exchange data in an easy manner. REST stands for Representational State Transfer. This was designed specifically for working with components such as media components, files, or even objects on a particular hardware device. Any web service that is defined on the principles of REST can be called a RestFul web service. A Restful service would use the normal HTTP verbs of GET, POST, PUT and DELETE for working with the required components. The benefits of REST API and the reasons why new technologies accepting REST API rather than SOAP service are described below: In addition to using HTTP for simplicity, REST offers a number of other benefits over SOAP: REST allows a greater variety of data formats such as Plain text, HTML, XML, JSON, etc. whereas SOAP only allows XML. Coupled with JSON (which typically works better with data and offers faster parsing), REST is generally considered easier to work with. REST offers better support for browser clients which credit goes to JSON, REST provides superior performance, particularly through caching for information that’s not altered and not dynamic. REST is the protocol used most often for major services such as Yahoo, Ebay, Amazon, and even Google. REST is generally faster and uses less bandwidth. It’s also easier to integrate with existing websites with no need to refactor site infrastructure. This enables developers to work faster rather than spend time rewriting a site from scratch. Instead, they can simply add additional functionality. SOAP requires more bandwidth for its usage. Since SOAP Messages contain a lot of information inside of it, the amount of data transfer using SOAP is generally a lot. Still, SOAP remains the preferred protocol for certain use cases. The general consensus among experts these days is that REST is the typically preferred protocol unless there’s a compelling reason to use SOAP (and there are some cases in which SOAP is preferred).

Project Name: Add Vegan and vegetarian column in subway.com 1. Planning Phase: Subway will add a Vegan column where vegetarian customers can find their foods easily. The column will be available for customers within 3 months and a budget was fixed for this project. 2. Requirement Analysis Phase: Customers can find all vegetarian items from this column with picture and can find the health benefits as well as price. This column could be operated from both PC and mobile application. 3. Design phase: As per requirement Green color with Vegetable pictured column was easy for customers to find the vegan button/column. Customers can find all vegetable items with price in this column. 4. Development Phase: As per requirement new column is built in Java to follow the existing subway page which was built in Java . Subway newly added column is ready to launch. 5. QA/Testing Phase: QA tester found newly added column is not accessible from mobile app which does not meet the requirement. They create a bug and send the developer to fix it. 6. Production/Maintenance Phase: After fixing the issue new column launched for the customers. Three months later one customer found one error on new column and inform through client help desk and QA team further analyze and send the developer to fix the problem. Developer fixed the issue and released the new version.