Software Testing without Requirements


Software Testing  without Requirements

Generally there are no applications without requirements, Software without documented requirements is a reality that unfortunately most of us face more often.

Suppose we have been handed an application with no requirements. We are supposed to test it. Can we do it? Sure, we can,

Sometimes, IT Companies develop Software Applications based on customer communication and by observing the Customer Business operations and without Documented Requirements, this type of situation is there most of the companies for some projects not for all projects.

Then How to Create Test Cases, usually we derive Test scenarios from requirements then document Test Cases, but in this scenario "No Requirements documentation but Application is ready", by exploring the application and using our past experience derive Test Scenarios, document Test cases, and execute the Test cases.

I am taking one sample application, It is an Online Shopping Application, 

Suppose I have given an Application for Testing, 

Domain: ECommerce
Sub-Domain: B2C (Business to Customer
Application: Online Shopping

Application Name is - gcrShop, developed in LAMP (Linux, Apache, MySQL, and PHP)

It has 3 important ant layers,
i) Admin Interface
ii User Interface
iii) Database Interface

They (Development Tea m and project management) gave URLs for Admin and User Interfaces and Admin Login details, no Login required for User Interface.

i) gcrShop Application Admin Interface
http://www.gcrit.com/build3/admin/

Admin Login Details:
                   Username: admin
                   Password: admin@123

ii) gcrShop Application User Interface
http://www.gcrit.com/build3/

And It has no documented Requirements, We need to Test this Application,

Steps:
1) Write Test Cases and Collect Test Data
2) Execute the Test cases
--------------------------------------------
1) Write Test Cases by exploring the Application and using previous experience (generally we derive Test Scenarios from Requirements), but we don't have Documented Requirements for this Application.

Hints:
i) Explore the Application
ii) Use Previous Experience 
iii) Communicate with Developers (If Required)
iv) Communicate with customer (If Required) 
Then Create and Execute Test Cases.... 
Software Testing Project
-----------------------------------------------------
First write Test Case names/Titles then Document the Test Cases...
i) Test Case for Admin Interface
http://www.gcrit.com/build3/admin/

1) Verify Launch Application (Admin Interface, Includes Launch Browser)

2) Verify Required Elements availability of Login Page

3) Verify Redirect Functionality before Login tot the Application (From Admin to User Interface) 

4) Verify Admin Login with valid input for Admin Interface of the Application

5) Verify Redirect Functionality after Login tot the Application (From Admin to User Interface) 

6) Verify Admin Login with Invalid input for Admin Interface of the Application

7) Verify Admin Login with 3 sets of Invalid data (Lock the Login Functionality for 5 minutes)

8) Verify Admin Login to Admin Interface after 5 minutes

9) Verify Required Elements availability in Admin Index Page

10) Verify Add Manufacturer

11) Verify Edit Manufacturer

12) Verify Delete Manufacturer

13) Verify Add Category

14) Verify Edit Category

15) Verify Delete Category

16) Verify Add Product

17) Verify Edit Product

18) Verify Delete Product

19) Verify Add Currency

20) Verify Edit Currency

21) Verify Delete Currency

22) Verify Set Default Currency

23) Verify Customer Report/s

24) Verify Product Report/s

25) Verify Log Off 
-----------------------------------------------------
ii) Test Case for User Interface
http://www.gcrit.com/build3/

1) Verify Launch the User Interface of the Application with valid URL

2) Verify Required Elements availability (Constant / Fixed Elements) of User 
Interface Home Page

3) Verify products "Search"...

4)  Verify products "Advanced Search"...

5) Verify "create an account" / Customer Registration with valid input data

6) Verify "create an account" / Customer Registration with invalid input data

7) verify "login"/Customer Login valid input data

8) verify "login"/Customer Login invalid input data

9) Verify "Shopping Cart" before Select any product

10) Verify "Shopping Cart" after Select any product/s

11) Verify "Update" in Shopping Cart while add a product

12) Verify "Update" in Shopping Cart after add a product

13) Verify "Remove" the Product from Shopping Cart

14) Verify "Checkout" before select any product and before Login

15) Verify "Checkout" after select any product/s and before Login

16) Verify "Checkout" before select any product and after Login

17) Verify "Checkout" after select any product/s and after Login

18) Verify "Change Address" with another Address

19) Verify availability of all Payment Methods

20) Verify Select "Payment Method"

21) Verify "CheckOut" Process

22) Verify "LogOff" Etc...
-----------------------------------------------------
Next Document these Test Cases, and Execute...

Also Read:

1) Writing a Sample Test Case

2) Automating a Manual Test Case

0 comments:

Post a Comment