Software Testing Fundamentals

Write a detailed test plan for a mobile APP for purchasing item (deal Fast). The App-deal Fast provides option for purchasing items as well as making payment through debit as well as credit card. Also write desired test documents, test cases and test strategies.

Test Plan for Deal Fast

1. Name of the Product: Deal Fast

2. Prepared by: ABC and XYZ Dated on 03/03/2011

3. Introduction:

• Deal Fast is an E-commerce company established in 2009 by ABC and XYZ. It operates exclusively in India with headquarters at Bangalore.
• It is offering to purchase electronic goods, books, sports equipment etc.
• It allows payment methods such as cash on delivery, payment through debit as well as credit card.

4. Test Plan Objectives:

• Define the activities required to develop and test the system.
• Communicate to all responsible parties the system test strategies.
• Define deliverables and responsible parties.

5. Scope:

• Login of Customer.
• Search for products what the user/customer wants exactly. Product details, product name, color, price, availability etc.
• Add into the Cart:
After selection of product get selected items into the cart for finalization.
• Payment:
After the product finalization customer has choices of any of the payment modes like Debit Card as well as Credit Card.
• View order
• Cancellation of order

6. Risks:

• Loss of mobile.
• Sometimes hacker may steal the user’s information. i.e., financial details, A/c Number, Password etc.

7. Test Strategy:

1. Unit testing

• This testing is the testing of individual modules.
• It is carried out to ensure the validity of a particular module.

2. Integrated Testing

• Integrated testing is the testing of the system modules.
• This is done to identify the errors which relate to the integration of different module.

3. System Testing

• It tests system against its initial objectives.
• It is done either in a simulated environment or in a live environment.

4. Validation Testing

• Where requirement established is a part of the software requirement analysis and it is validated against the software that has been established.

8. Environment Requirement:

• Smart phone is required.
• 256 RAM.
• 1 GB Hard disk.
• Android 2.1.2 version onwards.

9. Functions to be Tested:

• Login of Customer Page.
• Search Option.
• Insert Data Page.
• Update Data Page.
• Payment Security.

10. Test Cases for Mobile APP:

ID	Name	Description	Test Steps Input Output		Test Case Status	Priority
Login	Validation Login	Verify login details	Enter valid login id and password	Displays successful login message	Design	High
Search	Searching/Finding an item	Search particular item with image	Enter details of the item or product	Displays details of the item with image	Design	High
Order	Purchase item	Place order for an item or product	Displaying the details of item, Click on 'Buy' button for purchasing an item	Displays the Payment details page and shows the option for payment	Design	High
Payment 1	Debit Card Payment	Place the order with debit card	Click on the option 'Debit Card for Payment'	Displays the debit card details page	Design	High
Payment 2	Validate Debit Card	Verify card details	Enter valid details of debit card	Displays the order placed successful message	Design	High
Payment 3	Credit Card Payment	Place the order with credit card	Click on the option 'Credit Card for Payment'	Displays the credit card details page	Design	High
Payment 4	Validate Credit Card	Verify card details	Enter valid details of credit card	Displays the order placed successful message	Design	High

11. Test Deliverables:

• These are the documents that come out of the test cycle activity.
• The list of the test documents are as follows:
A. Test Plan
B. Test Cases Design Specifications
C. Test Scripts
D. Test Case Coverage Reports
E. Defects / Enhancement Logs
F. Test Reports

Explain different types of reviews with suitable examples?

What is Software Reviews?

• It is a process or meeting during which a software product is examined by a project personnel, managers, users, customers, user representatives etc.
• It finds the defects before they are passed on to other software engineering activity or released to the customer.

Types of Software Review



A. Walkthrough

• This is not a formal process.
• Walkthrough is led by the authors.
• Author guides the participants through the document according to his or her thought process to achieve a common understanding and to gather feedback.
• It is mostly useful for higher level documents like requirement specification etc.

B. Inspection

• Inspection is the most formal review type.
• Inspection is led by the trained moderators.
• In this process, the documents are prepared and checked thoroughly by the reviewers before the meeting.
• Inspection involves peers to examine the product.
• It improves the product quality.
• Inspection removes defects efficiently and as early as possible.
• This review process helps the author to improve the quality of the document under inspection.

C. Technical Review

• Technical review is the less formal review.
• Technical review is led by the trained moderators, but can also be led by the technical expert.
• This review is performed as a peer review without management participation.
• These reviews are vary from quite informal to very formal.

D. Informal Review

• These reviews are applied many times during the early stages of the life cycle of the document.
• The main goal of informal review is that to keep the author and improve the quality of the document.
• The most important thing about informal review is that they are not documented.

E. Formal Review

• This review follows a formal process.
• A Formal review is a well structured and regulated.

It consists of six main steps:

1. Planning
2. Kick-off
3. Preparation
4. Review meeting
5. Rework
6. Follow up

1. Planning

• This is the first step of the formal review.
• It begins with a request for a review by the author to the moderator.
• A moderator has to take care of the scheduling like date, time, place etc.

2. Kick-off

• It is an optional step in a review procedure.
• Kick-off gives a short introduction on the objectives of the review and the documents to the everyone.

3. Preparation

• In this step, the reviewers review the document individually using the related documents, procedures, rules and checklists provided.

4. Review meeting

This process consists of three phases:

I. Logging phase
II. Discussion phase
III. Decision phase

I. Logging phase: The issues and the defects are identified during the preparation step. It is done by the author or a scribe.
II. Discussion phase: If any issue needs discussion then the item is logged and then handled in the discussion phase.
III. Decision phase: At the end of the meeting a decision in the document under review has to be made by the participants. If the number of defects are found per page is more than a certain level, then the document must be reviewed again after it has been reworked.

5. Rework

• At this stage, the number of defects found per page exceeds the certain level, then the document has to be reworked.

6. Follow-up

• At this stage, the moderator check to make sure that the author has taken action on all known defects.