Android apps to use in appium android test examples

Breaking

Wednesday, March 21, 2018

without Requirements


Software Testing  without Requirements

Generally in that place are no applications without requirements, Software without documented requirements is a reality that unfortunately virtually of us facial expression upwards to a greater extent than often.

Suppose nosotros accept been handed an application amongst no requirements. We are supposed to exam it. Can nosotros produce it? Sure, nosotros can,

Sometimes, information technology Companies railroad train Software Applications based on client communication together with past times observing the Customer Business operations together with without Documented Requirements, this type of province of affairs is in that place virtually of the companies for about projects non for all projects.

Then How to Create Test Cases, ordinarily nosotros derive Test scenarios from requirements thence document Test Cases, exactly inward this scenario "No Requirements documentation exactly Application is ready", past times exploring the application together with using our past times sense derive Test Scenarios, document Test cases, together with execute the Test cases.

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

Suppose I accept given an Application for Testing, 

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

Application Name is - gcrShop, developed inward LAMP (Linux, Apache, MySQL, together with PHP)

It has three of import ant layers,
i) Admin Interface
ii User Interface
iii) Database Interface

They (Development Tea 1000 together with projection management) gave URLs for Admin together with User Interfaces together with 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 withdraw to Test this Application,

Steps:
1) Write Test Cases together with Collect Test Data
2) Execute the Test cases
--------------------------------------------
1) Write Test Cases past times exploring the Application together with using previous sense (generally nosotros derive Test Scenarios from Requirements), exactly nosotros don't accept Documented Requirements for this Application.

Hints:
i) Explore the Application
ii) Use Previous Experience 
iii) Communicate with Developers (If Required)
iv) Communicate amongst client (If Required) 
Then Create together with Execute Test Cases.... 
Generally in that place are no applications without requirements   without Requirements
-----------------------------------------------------
First write Test Case names/Titles thence 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 earlier Login tot the Application (From Admin to User Interface) 

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

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

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

7) Verify Admin Login amongst three sets of Invalid information (Lock the Login Functionality for five minutes)

8) Verify Admin Login to Admin Interface later five minutes

9) Verify Required Elements availability inward 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 amongst 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 amongst valid input data

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

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

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

9) Verify "Shopping Cart" earlier Select whatsoever product

10) Verify "Shopping Cart" later Select whatsoever product/s

11) Verify "Update" inward Shopping Cart spell add together a product

12) Verify "Update" inward Shopping Cart later add together a product

13) Verify "Remove" the Product from Shopping Cart

14) Verify "Checkout" earlier pick out whatsoever production together with earlier Login

15) Verify "Checkout" later pick out whatsoever product/s together with earlier Login

16) Verify "Checkout" earlier pick out whatsoever production together with later Login

17) Verify "Checkout" later pick out whatsoever product/s together with later Login

18) Verify "Change Address" amongst about other 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, together with Execute...

Also Read:

1) Writing a Sample Test Case

2) Automating a Manual Test Case

Sumber http://www.gcreddy.com/

No comments:

Post a Comment