Deliverable 6 – Test Plans And Deployment Scenario You are the lead developer for the software development team at Great Code Inc. Your company has been co

Click here to Order a Custom answer to this Question from our writers. It’s fast and plagiarism-free.

Deliverable 6 – Test Plans And Deployment Scenario
You are the lead developer for the software development team at Great Code Inc. Your company has been contracted by the Acme Company, a small manufacturing company, to develop a set of software system solutions to bring their existing manual, paper ordering process into an automated, digital online ordering system. The Acme Company has very limited experience with the process of developing software.
Instructions
The Program Manger has asked you to develop a test plan for the Acme Company online ordering system project that includes the following:

Ensure that at least three types of testing techniques are detailed within the test plan.
Construct at least three test cases within each type of testing technique.
Within each test case, detail the scope of the test case, the procedure in executing the test, and the success/failure criteria. Scenario

You are the lead developer for the software development team at Great Code Inc. Your company has been contracted by the Acme Company, a small manufacturing company, to develop a set of software system solutions to bring their existing manual, paper ordering process into an automated, digital online ordering system. The Acme Company has very limited experience with the process of developing software.

Instructions

The Program Manger has asked you to develop a test plan for the Acme Company online ordering system project that includes the following:

· Ensure that at least three types of testing techniques are detailed within the test plan.

· Construct at least three test cases within each type of testing technique.

· Within each test case, detail the scope of the test case, the procedure in executing the test, and the success/failure criteria.

1. Unit testing

2. Integration Testing

3. Acceptance testing

Unit Testing

In the unit testing, we need to test only a single unit which is also called as smallest piece od code that is logically written. In the programming sense, a function, a method is a unit.

Let us say you have three classes (For example)

1. Add Items to Cart

2. Pay bill

3. Store delivery details

Testcase-1:

Scope of the test case: This test case will be applied to only the piece of code which is in class “Add items to Cart”.

Procedure in executing the test:

a. Run the code and check if items added to the cart (queue/stack data structure)

b. Write test case for running the methods by adding sample data to cart.

Success/failure criteria.

a. If data is present in the data structure, success.

b. If data is not present, failure.

Testcase-2:

Scope of test case: In this test case, testing is done to the payment method, where it will check if the payment is done or not.

Procedure for executing the test:

a. Enter the amount and pay, check if the bank account of the business is crediting or not.

b. Write a test case, which will run the payment method by passing a sample amount and returns the account balance in return.

Success/failure criteria:

a. If the test function returns the balance as an updated one, it is a success.

b. If it does not return updated balance, failure.

Testcase-3:

Scope of test case: In this test case, you need to check the database if the delivery details got saved or not.

Procedure for executing the test:

a. Write a test case/query to check the database to find out if the delivery details are present in the database.

b. If the query returns all the columns as result, then it is done.

Success/failure criteria:

a. Success if the query returns all column data.

b. Failure of otherwise.

Integration Testing:

In this testing, we combine the individual modules we have already performing unit testing by joining all the modules into a single unit. By this, we can test the flow of executing an order.

Testcase-1: In this test case, we combine all the modules tested for the user interface and check if the navigation is happening correctly.

Scope of test case:

a. Combine all the individual methods and classes.

b. Write a test case method that will call each method one after the other.

Success/failure criteria:

a. If the test function executes the code such as navigation from one page to another page happens, then it is successful.

b. If one of the pages is not navigable, then it is a failure.

Testcase-2:  In this testcase, we need to check for the responsiveness of the User interface written in React or Javascript.

Scope of test case:

a. Combine all the modules into a single unit.

b. Write a test function that will open each page and check for its responsiveness by filling the form and submitting, clicking on buttons and all.

c. This testcase will test from starting login page to the last payment page.

Success/failure criteria:

a. If all the pages are responsive then success.

b. If not, failure.

Testcase-3:  In this, we will test the backend code which is the logic of code that is responsible for adding product to cart, payment, storage all at once.

Scope of test case:

a. Write a test function that will call one function after another that will return itemlist after adding items to the cart, payment balance after payment, and delivery details after storing data in the database.

b. It will test all modules right from adding items to payment.

Success/failure criteria:

a. If the cart is full, the payment balance is updated and the database has delivery details, then the testcase is successful.

b. If the cart is empty, then it is a failure.

Acceptance Testing:

In this testing, it is checked that if the product is acceptable to end-users.

Testcase-1: In this testcase, we will check if the system is able to open on the desktop website as well as mobile.

Scope of test case:

a. Open the website on a desktop/laptop and use the application.

b. Open and check the usability of the app on mobile as well.

Success/failure criteria:

a. If the app is able to open on both ends, then it is successful.

b. Failure if it fails to load on at least one end(mobile/desktop).

Testcase-2:  In this testcase, we need to check if the user interface is bootstrapped for small screens as well.

Scope of test case:

a. Try to open the website in the console and view it in mobile view.

b. Install its apk on mobile and try opening all the pages of the application.

Success/failure criteria:

a. If all the pages visible on the small screen are bootstrapped, then it is a success.

b. Failure if at least one of the pages is unorganized.

Testcase-3: In this testcase, we need to check if the user can perform all the activities from start to end on the app without any buffering/page loading issue.

Scope of test case:

a. Open the application multiple times and try a sample item ordering.

b. Try paying for the item from adding a card to getting OTP and authorizing the payment.

c. Try if you can see the delivery details and track the package.

Success/failure criteria:

a. If one of the above activities are buffer free and no blocker, then it is successful.

b. Failure if at least one of the activities hangs up.

References:

Application deployment and testing strategies | Solutions. (2020). Retrieved 21 December 2020, from https://cloud.google.com/solutions/application-deployment-and-testing-strategies

Software Development and Testing Methodologies (with Pros and Cons). (2020). Retrieved 21 December 2020, from https://www.softwaretestinghelp.com/software-development-testing-methodologies/

The different types of testing in Software | Atlassian. (2020). Retrieved 21 December 2020, from https://www.atlassian.com/continuous-delivery/software-testing/types-of-software-testing

Feedback:

Basic test plan ensures at least three types of testing techniques are included. (2)

The test plan identifies three types of testing techniques to be included. Each technique is described with minimal detail.

 

Less than three test cases within each type of testing technique included.(1)

The test cases are too vague or too broad. Most are not testable. For example “we need to check if the user can perform all the activities from start to end on the app without any buffering/page loading issue”. No tester could be expected to “perform all activities”. That is not descriptive enough. The test cases should be specific functions and behaviors that even a non software person could execute the test case and determine success or failure.

 

Vague scope of the test case included. (1)

You have the procedure steps to execute the test case labelled at the the scope. The scope is a short sentence that details what you testing. 

 

Procedure in executing the test is explicitly stated. (1) 

The procedures are too vague. In the unit test section, the procedure states to “write the test case”. These are the test cases so don’t understand what you mean in this step.

 

Minimal success/failure criteria noted(1)

The success/failure criteria are too vague. These should be objective, detail things you can observe within the system to verify that the system performed correctly or not.

Place your order now for a similar assignment and have exceptional work written by one of our experts, guaranteeing you an A result.

Need an Essay Written?

This sample is available to anyone. If you want a unique paper order it from one of our professional writers.

Get help with your academic paper right away

Quality & Timely Delivery

Free Editing & Plagiarism Check

Security, Privacy & Confidentiality