What is a test scenario? write atleast 15 test scenarios for gmail?

Question

Answer test scenario:- test # 1 scenario is the method

followed by the tester in which way the application are tested according to the user requirement intially first test gmail page has openning or not after that openning the web page see all the option are available in it like(loginid,password,forgot password,register etc) then see the login id is working and also password should be min 6 character to the 32 character should accept if any user forgot their password forgot password should work in the similar way test after entering to the home page also if all the option are working properly close test else if any error is there then report a defect to the test lead or project manager

Answer test scenario is a process # 3 where test engineer feels he

will do some testing on the application that situatio n is called Test scenario

Answer test scenario:- test # 4 scenario is the method

followed by the tester in which way the application are tested according to the user requirement intially first test gmail page has openning or not after that openning the web page see all the option are .1.Open gmail site. should be open properly without ask any pop message. 2.Gmail in define login name,and password,submit button in proper line.. 3.Check gui related to login,password,submit button. 4.Submitted password minimum

4 characters to 16 characters. 5.Check userliablity and userinterface related activity. 6.if user forgot login name and click to forgot name function should be work properly. 7.Open gmail check define Link and website name after click on that link should be go to properly that open newtabs/windows. 8.available in it like(loginid,password,forgot password,register etc) 9.then see the login id is working and also password should be min 6 character to the 32 character should accept 10.if any user forgot their password forgot password should work in the similar way test after entering to the home page also if all the option are working properly close test else if any error is there then report a defect to the test lead or project manager

Answer 1) Test whether Gmail # 5 page is opening or not.

2)

After the Gmail page

opens, check whether all the options are available in it(Username, password, stay signed in check-box, Sign in tab, Cant access your account hyperlink, create an account, etc) 3) Move the mouse cursor over all enterable text boxes (Username and Password). Cursor should change from arrow to insert bar. 4) Example of valid enterable form of username should appear below Username box. 5) Enter the user name only and try to login- you should get a message-Enter your password. 6) Enter the password only and try to login, you should get a message-enter your email address. 7) Enter invalid characters like!@$ %^&*() _+ in the username box and you should get a message invalid email address. 8) Move the mouse cursor over the sign in tab and it should glow. 9) Enter the correct username and incorrect password and you should get the

message- The username or password you entered is incorrect. 10) Enter the incorrect username and correct password and you should get the message-The username or password you entered is incorrect. 11) The cursor should jump from username box to password box by using the Tab key in the computer. 12) Whenever the cursor lands in either of the text boxes, it should get highlighted. 13) Then see if the login id is working by clicking on the sign in button as well as by clicking on Enter key in your computer. 14) Also password should be min 6 character to the 32 character should accept. 15) When you click on the Cant access your account it should take you to Google accounts page displaying the Email Address-enterable text box, submit tab, forgot your username, create a new Google account and try these trouble shooting tips- hyperlink. 16) When you click on the Create an account command

button, it should lead you to create a Gmail accountGmail screen. 17) All the hyperlinked text should be accessible in the Gmail sign in page. 18) Check for the aesthetic conditions of the Gmail sign in page.

Answer test scenario is a situation # 6 which a tester takes and

write test cases on it.Each test scenario might contain single or number of test cases. Test scenarios for the gmail page 1.enter the gmail url.page should open. 2.check for the availability of all the mandatory fields like username ,password,remember me.etc 3.Move the mouse cursor over all enterable text boxes (Username and Password). Cursor should change from arrow to insert bar. 4.enter different sets of correct usernames and passwords.Should be able to open account.

5.Try different sets of incorrect user names and correct passwords.Should get the messsage "The username or password you entered is incorrect." 6.try different sets of correct usernames and incorrect passwords.Should get the message " The username or password you entered is incorrect." 7.Try different sets of incorrect usernames and incorrect passwords.Should get the msg "The username or password you entered is incorrect." in this way you can wwrite many test scenarios

Answer test scenario is a situation # 7 which a tester takes and

write test cases on it.Each test scenario might contain single or number of test cases. Test scenarios for the gmail page 1.Click on IE8/Firefox mozilla. 2.enter the gmail url.page

should open. 3.Check GUI and Statement of Gmail Page. 4.Check Login name,password and submit button proper alignment. 5.check for the availability of all the mandatory fields like username ,password,remember me.etc 6.Check validate of Login name.(4 to 16/32 character). 7.Check validate of limit 16,17,31,32,33 character. 8.checking of String limit testing on login name minimum 4 character. 9.String security testing of Password. 10.Check string security testing of password(4 to 16 character.) 11.Check minimum range of password 4,5 character. 12.Check submit button properly Enable,disable. 13.Check Functionality of submit button ,submit valid data and click on submit button. 14.Check functionality of forgot pasword link. 15.Check Forgot pasword Link Enable/Disable. 26.Check Functionality of i can not access my account link. 27.Check "i can not access my account " Enable/Disable. 28.Check Create new account button Enable/or NOT .That

is defect to Gmail Site. he is not working.. 29.Check functionality of "Create new account button link". 30.Move the mouse cursor over all enterable text boxes (Username and Password). Cursor should change from arrow to insert bar. 31.enter different sets of correct usernames and passwords.Should be able to open account. 32.Try different sets of incorrect user names and correct passwords.Should get the messsage "The username or password you entered is incorrect." 33.try different sets of correct usernames and incorrect passwords.Should get the message " The username or password you entered is incorrect." 34.Try different sets of incorrect usernames and incorrect passwords.Should get the msg "The username or password you entered is incorrect." in this way you can wwrite many test scenarios

Answer Test Scenario is like end to # 8 end functionality of the one

scenario. It is like, Sending mail from gmail. If we take this as one scenario, We should follow the following steps to send th mail: 1. Open the gmail application 2. Enter credentials(User name and PWD) 3. Click on Compose button. 4. Enter To address, Subject, Data and etc. 5. Click on Send mail. 6. Check the mail in sent items. 7. Logout Gmail. This is the end to edn scenario. For all the above steps we can write test case for every step. For each and every action button we can write one test case.
Re: Need some 10 test scenarios for integration testing on Gmail. Answer #1

Integration Test Case Design forGmail.Com 26.Click on Compose link buttonThe compose mail page should bedisplayed26.1Enter User bs email id into TOtext filed,

enter user cs email id inBCC text field, add invitation,click on add to contacts & click onsend button The confirmation page should bedisplayed26.2Click on sent mail linka)The sent mail page should bedisplayedb)The first mail should be sent touser Bs email id in TO field& User Cs email id in BCCfield with attached invitationto both the users B&C26.3Click on Contacts linka)Contacts page should bedisplayedb)The users B&C email idsshould be displayed incontacts list26.4Click on Logout button in User AThe login page should be displayed26.5Login as User B with username &password The user b home page should bedisplayed26.6Click on Inbox linka)The inbox page should bedisplayedb)The first mail in user Bsaccount should have receivedwith invitation from user Asemail id26.7Click on Contacts pagea)The contacts page should bedisplayed b) The user As email id shouldnot be listed in contacts page26.8Click on Logout link button inuser B The login page should be displayed26.9Login as User C with userid &password The mail page of User c should bedisplayed26.10Click on Inbox linka)The inbox page should bedisplayedb)The first mail in user Csaccount should be displayedwith an invitation receivedfrom user As email id26.11Click on contacts linka)The

contacts page should bedisplayedb)In contacts user As email idshould not be listed27.Click on Compose link buttonThe compose mail page should bedisplayed27.1Enter User bs email id into TOtext filed, enter user cs email id inBCC text field, click on add tocontacts & click on save button The confirmation page should bedisplayed27.2Click on Draft mail linka)The draft items page shouldbe displayedb)The first mail in the draft itemsshould display user Bs email Pr@$@nth | 10 Assignment 8: Integration Test Case Design forGmail.Com id in TO field & User Csemail id in BCC field27.3Click on Contacts linka)Contacts page should bedisplayedb)The users B&C email idsshould be displayed incontacts list +VE INBOX TEST CASES 28.Login as User A with userid &passwordUser home page should bedisplayed28.1Click on Inbox linkInbox page should be displayed28.2Click on a mail in inboxSelected mail should be displayed28.3Click on reply button and Enterthe user bs email id in TO textfield and click on send buttona)Sent mail confirmation shouldbe displayed28.4Click on Sent items pagea)Sent items page should bedisplayedb)The reply mail &

actual mailshould be displayed in sentitems page28.5Click on Inbox linkThe actual and reply should bedisplayed in inbox also28.6Click on Logout link in User ALogin page should be displayed28.7Login as User b with user id &passwordUser Bs home page should bedisplayed28.8Click on Inbox items pagea)The inbox page should bedisplayedb)The mail sent from user Ashould be displayed29.Click on Inbox items page asUser A The inbox page should bedisplayed29.1Click on a mail in inbox which wehave selected The selected mail should bedisplayed29.2Click on Reply button, enter theUser Bs email id in TO field, addsome invitation & click on Sendbutton The sent mail confirmation pageshould be displayed29.3Click on Sent mail linka)The sent mail page should bedisplayedb)The reply mail and actual mailshould be displayed in sentmail items with attachedinvitation29.4Click on Inbox items linka)The inbox page should bedisplayedb)The reply mail and actual mailshould be displayed in first inattached invitation29.5Click on Logout linkThe login page should be displayed29.6Login as User B with userid andPassword The user B home page should bedisplayed29.7Click on Inbox pagea)Inbox items should bedisplayedb)The first mail should bedisplayed with an invitationfrom User A Pr@$@nth | 11

Assignment 8: Integration Test Case Design forGmail.Com 30.Click on Inbox linkInbox items page should bedisplayed30.1Click on a selected mailThe selected mail should bedisplayed30.2Click on reply button link, addUser B email id in TO text field, addattachment & click on Send button The sent mail confirmation shouldbe displayed30.3Click on Sent mail linka)The sent items page should bedisplayedb)The reply mail and actual mailshould be displayed withattachment30.4Click on inbox linka)The inbox item should bedisplayedb)The reply mail should bedisplayed30.5Click on Logout linkLogin page should be displayed30.6Login as User B with user id &passwordUser Bs Home should be displayed30.7Click on Inbox page linka)The inbox items should bedisplayedb)The mail from user A shouldbe displayed with anattachment31.Click on Inbox linkInbox items page should bedisplayed31.1Click on a selected mailThe selected mail should bedisplayed31.2Click on Reply button link, adduser Bs email id in TO text field,add attachment & click on Savebutton The confirmation of sent mailshould be displayed31.3Click on Drafts items pagea)Draft items page should bedisplayed b) The mail should be displayed in

To field user B's email idwith attachment Pr@$@nth | 12

Definition and Terminologies:

In Integration Testing, individual software modules are integrated logically and tested as a group. A typical software project consists of multiple software modules, coded by different programmers. Integration testing focuses on checking data communication amongst these modules. Hence it is also termed as I & T (Integration and Testing), String Testing and sometimes Thread Testing.

Need of Integration Testing:

Although each software module is unit tested, defects still exist for various reasons like

Integration Test Case:

A Module in general is designed by an individual software developer who understanding and programming logic may differ from other programmers. Integration testing becomes necessary to verify the software modules work in unity At the time of module development, there wide chances of change in requirements by the clients. These new requirements may not be unit tested and hence integration testing becomes necessary. Interfaces of the software modules with the database could be erroneous External Hardware interfaces, if any, could be erroneous Inadequate exception handling could cause issues.

Integration Test case differs from other test cases in the sense it focuses mainly on the interfaces & flow of data/information between the modules. Here priority is to be given for the integrating links rather than the unit functions which are already tested. Sample Integration Test Cases for the following scenario:Application has 3 modules say Login Page, Mail box and Delete mails and each of them are integrated logically. Here do not concentrate much on the Login Page testing as its already being done. But check how its linked to the Mail Box Page. Similarly Mail Box: Check its integration to the Delete Mails Module.

Test Case ID 1

Test Case Objective Check the interface link between the Login and Mailbox module Check the interface link

Test Case Description Enter login credentials and click on the Login button From Mail box select

Expected Result To be directed to the Mail Box

Selected email should appear in the Deleted/Trash folder

between the Mailbox and Delete Mails Module

the an email and click delete button

Approaches/Methodologies/Strategies of Integration Testing:

The Software Industry uses variety of strategies to execute Integration testing , viz. Big Bang Approach : Incremental Approach: which is further divided into following o Top Down Approach o Bottom Up Approach o Sandwich Approach - Combination of Top Down and Bottom Up Below are the different strategies, the way they are executed and their limitations as well advantages.

Big Bang Approach:

Here all component are integrated together at once, and then tested.

Advantages:

Convenient for small systems.

Disadvantages:

Fault Localization is difficult. Given the sheer number of interfaces that need to be tested in this approach, some interfaces links to be tested could be missed easily. Since the integration testing can commence only after all the modules are designed, testing team will have less time for execution in the testing phase. Since all modules are tested at once, high risk critical modules are not isolated and tested on priority. Peripheral modules which deal with user interfaces are also not isolated and tested on priority.

Incremental Approach:
In this approach, testing is done by joining two or more modules that are logically related. Then the other related modules are added and tested for the proper functioning. Process continues until all of the modules are joined and tested successfully. This process is carried out by using dummy programs called Stubs and Drivers. Stubs and Drivers do not implement the entire programming logic of the software module but just simulate data communication with the calling module. Stub: Is called by the Module under Test. Driver: Calls the Module to be tested. Incremental Approach in turn is carried out by two different Methods: o Bottom Up o Top Down

Bottom up Integration
In the bottom up strategy, each module at lower levels is tested with higher modules until all modules are tested. It takes help of Drivers for testing Diagrammatic Representation:

Advantages:

Fault localization is easier. No time is wasted waiting for all modules to be developed unlike Big-bang approach Critical modules (at the top level of software architecture) which control the flow of application are tested last and may be prone to defects. Early prototype is not possible

Disadvantages:

Top down Integration:

In Top to down approach, testing takes place from top to down following the control flow of the software system. Takes help of stubs for testing. Diagrammatic Representation:

Advantages:

Fault Localization is easier. Possibility to obtain an early prototype. Critical Modules are tested on priority; major design flaws could be found and fixed first. Needs many Stubs. Modules at lower level are tested inadequately.

Disadvantages:

Integration Testing Procedure

The integration test procedure irrespective of the test strategies (discussed above): 1. Prepare the Integration Test Plan 2. Design the Test Scenarios, Cases, and Scripts. 3. Executing the test Cases followed by reporting the defects. 4. Tracking & re-testing the defects. 5. Steps 3 and 4 are repeated until the completion of Integration is successfully.

Brief Description of Integration Test Plans:

It includes following attributes: Methods/Approaches to test (as discussed above). Scopes and Out of Scopes Items of Integration Testing. Roles and Responsibilities. Pre-requisites for Integration testing. Testing environment. Risk and Mitigation Plans.

Entry and Exit Criteria.

Entry and Exit Criteria to Integration testing phase in any software development model Entry Criteria: Unit Tested Components/Modules

All High prioritized bugs fixed and closed All Modules to be code completed and integrated successfully. Integration test Plan, test case, scenarios to be signed off and documented. Required Test Environment to be set up for Integration testing Exit Criteria: Successful Testing of Integrated Application. Executed Test Cases are documented All High prioritized bugs fixed and closed Technical documents to be submitted followed by release Notes.

Best Practices/ Guidelines for Integration Testing

First determine the Integration Test Strategy that could be adopted and later prepare the test cases and test data accordingly. Study the Architecture design of the Application and identify the Critical Modules. These need to be tested on priority. Obtain the interface designs from the Architectural team and create test cases to verify all of the interfaces in detail. Interface to database/external hardware/software application must be tested in detail. After the test cases, its the test data which plays the critical role. Always have the mock data prepared, prior to executing. Do not select test data while executing the test cases.

Disadvantages
DEFINITION White Box Testing (also known as Clear Box Testing, Open Box Testing, Glass Box Testing, Transparent Box Testing, Code-Based Testing or Structural Testing) is a software testing method in which the internal structure/design/implementation of the item being tested is known to the tester. The tester chooses inputs to exercise paths through the code and determines the appropriate outputs. Programming know-how and the implementation knowledge is essential. White box testing is testing beyond the user interface and into the nitty-gritty of a system. This method is named so because the software program, in the eyes of the tester, is like a white/transparent box; inside which one clearly sees. White Box Testing is contrasted with Black Box Testing. View Differences between Black Box Testing and White Box Testing. EXAMPLE A tester, usually a developer as well, studies the implementation code of a certain field on a webpage, determines all legal (valid and invalid) AND illegal inputs and verifies the outputs against the expected outcomes, which is also determined by studying the implementation code. LEVELS APPLICABLE TO

White Box Testing method is applicable to the following levels of software testing:

Unit Testing: For testing paths within a unit Integration Testing: For testing paths between units System Testing: For testing paths between subsystems

However, it is mainly applied to Unit Testing. WHITE BOX TESTING ADVANTAGES

Testing can be commenced at an earlier stage. One need not wait for the GUI to be available. Testing is more thorough, with the possibility of covering most paths.

WHITE BOX TESTING DISADVANTAGES

Since tests can be very complex, highly skilled resources are required, with thorough knowledge of programming and implementation. Test script maintenance can be a burden if the implementation changes too frequently. Since this method of testing it closely tied with the application being testing, tools to cater to every kind of implementation/platform may not be readily available. White Box Testing is like the work of a mechanic who examines the engine to see why the car is not moving.

Definition by ISTQB

white-box testing: Testing based on an analysis of the internal structure of the component or system. white-box test design technique: Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system

what is Black Box Testing?

Black box testing is a software testing techniques in which functionality of the software under test (SUT) is tested without looking at the internal code structure, implementation details and knowledge of internal paths of the software.This type of testing is based entirely on the software requirements and specifications.

In Black Box Testing we just focus on inputs and output of the software system without bothering about internal knowledge of the software program.

The above Black Box can be any software system you want to test. For example : an operating system like Windows, a website like Google ,a database like Oracle or even your own custom application. Under Black Box Testing , you can test these applications by just focusing on the inputs and outputs without knowing their internal code implementation.

Black box testing - Steps

Here are the generic steps followed to carry out any type of Black Box Testing. Initially requirements and specifications of the system are examined. Tester chooses valid inputs (positive test scenario) to check whether SUT processes them correctly . Also some invalid inputs (negative test scenario) are chosen to verify that the SUT is able to detect them. Tester determines expected outputs for all those inputs. Software tester constructs test cases with the selected inputs. The test cases are executed. Software tester compares the actual outputs with the expected outputs. Defects if any are fixed and re-tested.

Types of Black Box Testing

There are many types of Black Box Testing but following are the prominent ones Functional testing This black box testing type is related to functional requirements of a system; it is done by software testers. Non-functional testing This type of black box testing is not related to testing of a specific functionality , but non-functional requirements such as performance, scalability, usability. Regression testing Regression testing is done after code fixes , upgrades or any other system maintenance to check the new code has not affected the existing code.

Tools used for Black Box Testing:

Tools used for Black box testing largely depends on the type of black box testing your are doing. For Functional/ Regression Tests you can use - QTP For Non-Functional Tests you can use - Loadrunner

Black box testing strategy:

Following are the prominent test strategy amongst the many used in Black box Testing Equivalence Class Testing: It is used to minimize the number of possible test cases to an optimum level while maintains reasonable test coverage. Boundary Value Testing: Boundary value testing is focused on the values at boundaries. This technique determines whether a certain range of values are acceptable by the system or not.It is very useful in reducing the number of test cases. It is mostly suitable for the systems where input is within certain ranges.

Decision Table Testing: A decision table puts causes and their effects in a matrix. There is unique combination in each column.

Comparison of Black Box and White Box Testing:

While White Box Testing (Unit Testing) validates internal structure and working of your software code, the mainfocus of black box testing is on the validation of your functional requirements. To conduct White Box Testing , knowledge of underlying programming language is essential. Current day software systems use a variety of programming languages and technologies and its not possible to know all of them. Black box testing gives abstraction from code and focuses testing effort on the software system behaviour. Also software systems are not developed in a single chunk but development is broken down in different modules.Black box testing facilitates testing communication amongst modules (Integration Testing) . In case you push code fixes in your live software system , a complete system check (black box regression tests) becomes essential. Though White box testing has its own merits and help detect many internal errors which may degrade system performance

Black Box Testing and Software Development Life Cycle (SDLC)

Black box testing has its own life cycle called Software Test Life Cycle (STLC) and it is relative to every stage of Software Development Life Cycle. Requirement This is the initial stage of SDLC and in this stage requirement is gathered. Software testers also take part in this stage. Test Planning & Analysis Testing Types applicable to the project are determined. A Test Plan is created which determines possible project risks and their mitigation. Design In this stage Test cases/scripts are created on the basis of software requirement documents Test Execution- In this stage Test Cases prepared are executed. Bugs if any are fixed and retested.