Test Cases for compose box In Mail

How to write a test case on compose box in mail?

Functional Tests	System Tests (Load Tests)
Checkout whether On clicking Compose mail, takes you to "Compose mail page"	---
Check whether it has a) To, Cc, Bcc to enter email address. b) Subject, to enter the subject of the mail c) Text body, space to enter the text.	---
Check whether a) To, Cc, Bcc accepts text. b) Subject, accepts text. c) Text body, accepts text	a) The number of email addresses that can be entered in To, Cc, and Bcc b) The maximum length of the subject c) The maxim no of words that can be entered in the text space
Check whether a) In To, Cc, Bcc, you can delete, edit, cut, copy, paste text. b) Subject, you can delete, edit, cut, copy, paste text. c) Text body, you can delete, edit, cut, copy, paste text and format text.
Check whether you can attach a file	a) The maximum size of the file that can be attached b) The max no of files that can be attached.
Check whether you can send, save or discard the mail

Performance Testing:---------------If sending mail, receiving mail etc are considered, then we could test the performance of the email server as:
1) Like if one user is connected, what is the time taken to receive a single mail.
2) If 1000s of users are connected, what is the time taken to receive the same mail.
3) If 1000s of users are connected, what is the time taken to receive a huge attachment file.

Usability Testing:-------------------
1) In Usability testing, we can check that, if a part of the email address is entered, the matching email addresses are displayed
2) If the mail is tried to send without the subject or “body of the text”, a warning is displayed.
3) If the To, Cc, Bcc contain an address, without @, it should immediately display a warning that the mail id is invalid.
4) Composing mails should be automatically stored as drafts. You can add some more testcases

Test Cases For Login Window

How to write test case of Login window ?

To check whether the entered User name and Password are vaild or Invaild PREPAIRED BY TESTERINFO
TEST CASE NO:- Authentication
Test DATA USER Name = COES and PASSWORD = COES
Step No Steps Data Expected Results Actual Results

1 Enter User Name and press LOGIN Button User Name= COES Should Display Warning Message Box "Please Enter User name and Password"

2 Enter Password and press LOGIN Button Password= COES Should Display Warning Message Box "Please Enter User name and Password"

3 "Enter user Nameand Password and press LOGIN Button" "USER = COES AND Password = XYZ" Should Display Warning Message Box "Please Enter User name and Password"

4 Enter user Name and Password and press LOGIN Button "USER = XYX AND Password = COES" Should Display Warning Message Box "Please Enter User name and Password"

5 "Enter user Name and Password and press LOGIN Button" "USER = XYZ AND Password = XYZ" Should Display Warning Message Box "Please Enter User name and Password"

6 "Enter user Name and Password and press LOGIN Button" "USER ="" "" AND Password = "" """ Should Display Warning Message Box "Please Enter User name and Password"

7 Enter User Name and Password and press LOGIN Button "USER = COES AND Password = COES" Should navigate to CoesCategoryList.asp page.

8 Enter User Name and Password and press LOGIN Button "USER = ADMIN AND Password = ADMIN" Should navigate to Maintenance page page. I Hope

Integration Testcases

How to write Integration Testcases?

Design document will contail all the system components so referring it OR through traceability matrix it describe the maping between FRS and testcases --u can write integration

"Integration Test Cases are written based on logical design to ensure complete coverage of all logical design elements."

In integration testing you need to write test cases for the Interface between the modules, For eg: if you are writing test cases for the integration of 3 modules M1, M2 and M3. you need to write the test cases for the individual behaviour of M1, M2 and M3. After that you need to write the test cases for their combinations like when we integrate M1 and M2, to test how will be the behaviour of M1+M2 and to verify the interface between them. in the same way for the combinations of M2, M3 M3,M1 and M1, M2 and M3. Here when we are integrating different modules, u need to write test cases to verify mainly the interface between the modules and to verify wheather the behaviour is meeting the requirements. The Integration test cases will be in the same format of normal testcases, but with some more additional fields like, Modules integrated.

Test Cases For Withdraw Module In Banking

test case for withdraw module in banking proj...

Step1: when the balance in the account is nill, try to withdraw some amount(amount>0) should display msg as " insufficient funds in acc"
step 2:when the account has some balance amount, try to withdraw amount(amount>balance amount in account), should display "insufficient funds in acc"
step 3: when the account has some balance amount, enter a amount (amount<=balance amount), should withdrawn correct amount from account. step 4: when the account has some balance amount, enter the amount as 0, should display msg as withdrawl amount should be > 0 and should be in multile of hundreds( varies depending on reqs docs).
In the case of Minimum balance mandatory in the Account:
step 5: When the account has balance amount, try to withdraw whole amount , should display msg as " Minimum balance should be maintained".
step 6: When the account has balance amount=minimum balance, try to withdraw any amount , should display msg as " Minimum balance should be maintained".

Test cases, suites, scripts, and scenarios

A test case is a software testing document,which consists of event, action, input, output, expected result, and actual result. Clinically defined (IEEE 829-1998) a test case is an input and an expected result. This can be as pragmatic as 'for condition x your derived result is y', whereas other test cases described in more detail the input scenario and what results might be expected.

The term test script is the combination of a test case, test procedure, and test data. Initially the term was derived from the product of work created by automated regression test tools. Today, test scripts can be manual, automated, or a combination of both.

The most common term for a collection of test cases is a test suite. The test suite often also contains more detailed instructions or goals for each collection of test cases. It definitely contains a section where the tester identifies the system configuration used during testing. A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests.

Collections of test cases are sometimes incorrectly termed a test plan. They might correctly be called a test specification. If sequence is specified, it can be called a test script, scenario, or procedure.

Test Cases For MS Word

Write test cases for copy & paste in MS Word

For negative testing of copy n paste we check for all other commands of the package, like-

1)Pressing copy on selected content - it should not bold / italic etc.
2)on pressing highlighted content should not cut.

For positive testing of copy we can design test cases like –
1) It should be dehighlited if no content is selected.
2) Copy icon and command should be highlighted just after selecting any content.
3) Without any selection when we press hot key “ctrl+c” it should display clipboard.
4) It should copy again n again to different selections and store it on the clipboard.
5) It should copy content with their formats.

For Paste-
1) paste icon and command should be dehilighted at beginning.
2) It should highlited just after copy something.
3) It should paste same content with their styles when we use hot key/ command/ icon.
4) It should paste n time, same content(last copied content).
5) It should paste copied content from clipboard as per our selection from clipboard.

Test Cases For Pen

what can be the various test cases for a pen?

1.To check the pen company
2.to check the pen type
3.to check the pen cap is present or not
4.to check the pen ink is filled or not
5. to check the pen writing or not
6.to check the ink color i.e black ro blue
7.to check the pen color
8.to check weather the pen is used to write all types of papers or not
9.to check the ink capacity of the pen
10.to check the pen product by fiber or plastic or glass
11 to check how long the pen is going to write
12)to check Type of pen (ink,ball,dot etc.).
13)to check Able to write (bold/thin)
14)Grip of the in hand (how comforting is it to hold and write with it?)
15)Type of ink required (ink,gel, fluid, refillable??)
16)Does it have a pocket holding gripe for better carriage.
17)Does the ink leaks in hot conditions or it seizes to flow in cold conditions
18)throw the pen down on floor..to check how much brittle it is ,is it broke down or not.

The test cases should be of high standards.
1.Functional test cases (here we test the functionality of pen e.g. writing in flow or not etc.)
2.User-Interface test caes ( look n feel of pen e.g. cap facility, easy to hold, should be attractive etc.)
3. Stress Testing ( check the temperature dependency e.g can it work if temp is high or low etc.)
4. Performance Testingif we categories every problem then we can write much test cases for that.

Test Cases For Computer Keyboard

write a test case for computer keyboard

useriNterface case:
check the clor of the key board
check the color of letters on the keys
check the height and width of the key board
keyboard keys should be as per the ANSI standard
keyboard should be plateform independent
keys are mapping with the commands
check the serial or parallel port
check if keybooard is detect by all bios setup
check that keyboard can be plugged into all PS/2 ports made by different manufacturers
check if keyboard is working without any driver installed ( assuming a normal keyboard )
check the total no of keys in that keyboard
check the keyboard wire length

functional case:
check if light glows when num lock is on
check if light glows when caps is on
check if key board can be connnected to CPU using cable.
check the functionality of all the numaric keys on key board(when pressed that particulay number should be dispalyed on the moniter)
check the functionality of all the character keys on key board(when pressed that particulay character should be dispalyed on the moniter)
check the functionality of caps,shift,ctrl,alt key.
check if all the keys on the right side(numaric are functionaning well)
check the functionality of arrown keys
check the functionality with ctrl+(any key) combination of keys
check the functionality with shift +(any key) combination of keys
check the print screen keythere are
check the keyboard color i.e white or black
many more case like this...

Test Cases for Mobile Phone

Write test cases for cell phone

1)Check whether Battery is inserted into mobile properly
2)Check Switch on/Switch off of the Mobile
3)Insert the sim into the phone n check
4)Add one user with name and phone number in Address book
5)Check the Incoming call
6)check the outgoing call
7)send/receive messages for that mobile
8) Check all the numbers/Characters on the phone working fine by clicking on them..
9)Remove the user from phone book n check removed properly with name and phone number
10) Check whether Network working fine..
11)If its GPRS enabled check for the connectivity
12)Check whether the items are displayed properly
13)Click on all the settings in the mobile- verify whether they are functioning properly.
14)Delete the user from the mobile- verify whether the user is deleted from the phonebook
15)Verify it is user friendly or not by clicking the menu.

Test Cases For White Paper

Write Test Cases on white paper.(For e.g. A4 size)

1)Check size of a page.
2)check quality od paper by using different pen and pencils.
3)check use of whitener on paper.
4)check erase.
5)check out the colour of the page
6)to check the paper quality
7)to check the paper thickness
8)to check the A4 sheet empty or not(Writed or Not)
9)to check weather it is folded or not
10)to check the company of the A4 Sheet

Included some pseudo code>

1)Check size of a page.assert
(page.width()==A4.WIDTH)assert(page.width()==A4.HEIGHT)assert(page.colour()==Color.WHITE)assert(page.density()==PAPER.GSM(80))>
2)check quality od paper by using different pen and pencils.[try to write with pen]assert(page.untorn())assert(page.contains(writing_from_pen)>
3)check use of whitener on paper.page.addwhitener(W)assert(page.whitened())>
4)check erase.page.erase(writing_from_pen) assert(page.is_blank())

Test Cases For defined "data type"

write test cases to test a new defined "data type" designed as required for a client? -
asked in a interview, company - "Oracle".

In general, a defined new data type in any language or any package

1 First we have to check the new defined data type is available in that particular
environment or not

2 whether the new defined data type is supported that particular environment or not.

3 whether the new defined data type is accepted specified Data or not.

4 Lower bound for that datatype (as each datatype has some lower limit), also check lower
limit -1

5 Upper bound for that datatype (as each datatype has some upper limit too), also check lower limit +1

6 also check any intermediate value too.All this is valid for scalar data types.

TYPES OF TEST CASES

TYPES OF TEST CASES

Test cases are broadly divided into two types.

1. G.U.I Test Cases.
2. Functional test cases.

Functional test cases are further divided into two types.

1. Positive Test Cases.
2. Negative Test Cases.

GUIDELINES TO PREPARE GUI TEST CASES:

1. Check for the availability of all the objects.
2. Check for the alignments of the objects if at all customer has specified the requirements.
3. Check for the consistence of the all the objects.
4. Check for the Spelling and Grammar.
Apart from these guidelines anything we test with out performing any action will fall under GUI test cases.

GUIDELINES FOR DEVELOPING POSITIVE TEST CASES.

1. A test engineer must have positive mind setup.
2. A test engineer should consider the positive flow of the application.
3. A test engineer should use the valid input from the point of functionality.

GUIDELINES FOR DEVELOPING THE NEGATIVE TEST CASES:

1. A test engineer must have negative mind setup.
2. He should consider the negative flow of the application.
3. He should use at least one invalid input for a set of data.

Test Case Design Techniques

Test Case Design Techniques

The test case design techniques are broadly grouped into two categories: Black box techniques, White box techniques and other techniques that do not fall under either category.

Black Box (Functional)
- Specification derived tests
- Equivalence partitioning
- Boundary Value Analysis
- State-Transition Testing

White Box (Structural)
- Branch Testing
- Condition Testing
- Data Definition - Use Testing
- Internal boundary value testing

Other
- Error guessing

A Test Case Format - Simple One

Test Case – Sample Structure

The manner in which a test case is depicted varies between organizations. Anyhow, many test case templates are in the form of a table, for example, a 6-column table with fields:

Test Case ID
Test Case Description
Test Dependency/Setup
Input Data Requirements/Steps
Expected Results
Actual Results
Status-Pass/Fail

Test Case

A test case is a detailed procedure that fully tests a feature or an aspect of a feature. While the test plan describes what to test, a test case describes how to perform a particular test. You need to develop test cases for each test listed in the test plan.

“A test case is a document specifying inputs, predicts results, and a set of execution conditions for a test item”.

"A test case is a unique combination od input and output."

Test Case gives you a great starting point for writing automation. Writing test cases is a crucial first step before writing test code.

how to design test cases in a generic manner:

1.Understand the requirements document.
2.Break the requirements into smaller requirements (if it improves your testability).
3.For each Requirement, decide what technique you should use to derive the test cases. For example, if you are testing a Login page, you need to write test cases
basing on error guessing and also negative cases for handling failures.
4.Have a Traceability Matrix as follows:

Needs to keep in mind general guidelines that will aid in test case design:

a. The purpose of each test case is to run the test in the simplest way possible. [Suitable techniques - Specification derived tests, Equivalence partitioning]

b. Concentrate initially on positive testing i.e. the test case should show that the software does what it is intended to do. [Suitable techniques - Specification derived tests, Equivalence partitioning, State-transition testing]

c. Existing test cases should be enhanced and further test cases should be designed to show that the software does not do anything that it is not specified to do i.e. Negative Testing [Suitable techniques - Error guessing, Boundary value analysis, Internal boundary value testing, State-transition testing]

d. Where appropriate, test cases should be designed to address issues such as performance, safety requirements and security requirements [Suitable techniques - Specification derived tests]

e. Further test cases can then be added to the unit test specification to achieve specific test coverage objectives. Once coverage tests have been designed, the test procedure can be developed and the tests executed [Suitable techniques - Branch testing, Condition testing, Data definition-use testing, State-transition testing]

Test Case Development

Test Case

A test case is a detailed procedure that fully tests a feature or an aspect of a feature. While the test plan describes what to test, a test case describes how to perform
a particular test. You need to develop test cases for each test listed in the test plan.

General Guidelines

As a tester, the best way to determine the compliance of the software to requirements is by designing effective test cases that provide a thorough test of a unit.

Various test case design techniques enable the testers to develop effective test cases. Besides, implementing the design techniques, every tester needs to keep in
mind general guidelines that will aid in test case design:

a. The purpose of each test case is to run the test in the simplest way possible. [Suitable techniques - Specification derived tests, Equivalence partitioning]

b. Concentrate initially on positive testing i.e. the test case should show that the software does what it is intended to do. [Suitable techniques - Specification derived

tests, Equivalence partitioning, State-transition testing]

c. Existing test cases should be enhanced and further test cases should be designed to show that the software does not do anything that it is not specified to do i.e.

Negative Testing [Suitable techniques - Error guessing, Boundary value analysis, Internal boundary value testing, State-transition testing]

d. Where appropriate, test cases should be designed to address issues such as performance, safety requirements and security requirements [Suitable techniques -

Specification derived tests]

e. Further test cases can then be added to the unit test specification to achieve specific test coverage objectives. Once coverage tests have been designed, the test
procedure can be developed and the tests executed [Suitable techniques - Branch testing, Condition testing, Data definition-use testing, State-transition testing]