Explore topic-wise InterviewSolutions in .

ADHOC testing is a negative testing, testing DONE with an unexpected SITUATION or that 's not there in the REQUIREMENT DOCUMENTS

Adhoc testing is a negative testing, testing done with an unexpected situation or that 's not there in the requirement documents

FUNCTIONAL testing is a testing DONE on function by GIVING some INPUT and expecting some OUTPUT.

functional testing is a testing done on function by giving some input and expecting some output.

GRAY BOX TESTING is the COMBINATION of UNIT testing and black box testing.

gray box testing is the combination of unit testing and black box testing.

Ramp testing increases the no of user in a particular TIME frame to know tha MAX no of user that it can ACCOMMODATE before THROWING ERROR messages.

Ramp testing increases the no of user in a particular time frame to know tha max no of user that it can accommodate before throwing error messages.

scalability testing is DONE to know how many EXTRA users can USE the APPLICATION beyond the load SPECIFIED.

scalability testing is done to know how many extra users can use the application beyond the load specified.

soak TESTING is a testing done to see how long the SYSTEM can with stand with the no of users for a particular duration of TIME.

soak testing is a testing done to see how long the system can with stand with the no of users for a particular duration of time.

STATIC checking is primarily the SYNTAX checking or a MANUAL review of the CODE.

Static checking is primarily the syntax checking or a manual review of the code.

1. to CHECK the keyboard company
2. to check the keyboard category i.e normal keyboard or MULTIMEDIA keyboard.to check the total no of keys in that keyboard
3. to check the keyboard type i.e normal or PS/2
4. to check the keyboard color i.e white or black
5. to check default NumLock should be in on condition
6. Default the CAPS lock and scroll lock should be in off condition
7. to check the keyboard WIRE length
8. to check all keys are WORKING properly or not

According to me following things could be tested:

• CAPACITY of the lift
• USABILITY (whether it's easy to operate or not)
• Functionality( whether it functions properly or not)
• comfort (whether a person is comfortable in it or not)
• height
• weight
• volume
• time it takes to reach every FLOOR
• test for maximum capacity of the lift
• test for more than max capacity
• check the working in case of a POWER failure

According to me following things could be tested:

Login window:

• focus to window to height,width of the TEXT boxes
• ENTER username for allow LOWERCASE, special characters (some of char allow only),numericals.
• PASSWORD, which is encrypted only allow
• then ENABLE "ok"button.
• if miss matching of any username password then it display the warning message window

Login window:

Test case for telephone:

1. To check connectivity of telephone LINE or cable
2. To check the modem to determine whether it is functioning or not
3. To check dial tone of the phone
4. To check the keypad while you dial any VALID number on the phone
5. To check ring tone with its volume levels
6. To check voice of both SIDES (from and to) of the phone
7. To check display monitor if the phone has
8. To check redial option whether its functioning or not
9. To check the company standard of phone
10. To check the weight and COLOR of the phone
11. To check loud speaker whether it is functioning or notany missing above then you can add any more test cases

Test case for telephone:

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 & 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 & Check removed properly with name and phone number
10. Check whether Network working fine..
11. If it's GPRS enabled Check for the connectivity.

Test cases for mouse (few)

Mainly CHECK mouse is attached system, color, check it buttons on it. ETC

• Objective is to VERIFY that when we click the right mouse button is it going to open list of that particular file or anything. DESCRIPTION(test case) is point to one file or anything and click the right mouse button Expected is it opens the list regarding that file (eg:list includes properties and etc).
• Objective is to verify that when we click the LEFT mouse button twice is it going to open that particular file or not. Description is point to one file and double click on that expected is it open that particular file.
• Objective is to verify the scroll button scroll the particular page or not Description is point to one page or file and use the scroll button Expected is it scrolls the page down or up.

Test cases for mouse (few)

Mainly check mouse is attached system, color, check it buttons on it. etc

ESSENTIALLY a test case is a document that carries a Test Case ID no, TITLE, type of test being conducted, Input, Action or Event to be performed, expected OUTPUT and whether the Test Case has ACHIEVED the desired Output(Yes No).

Basically Test cases are based on the Test Plan, which includes each module and what to be tested in each module. Further each action in the module is further divided into testable components from where the Test Cases are derived.

Since the test case handles a single event at a time normally, as long as it REFLECTS its relation to the Test plan, it can be called as a good test case. It does not matter whether the event passes or fails, as long as the component to be tested is addressed and can be related to in the Test Plan, the Test Case can be called a good Test Case.

Essentially a test case is a document that carries a Test Case ID no, title, type of test being conducted, Input, Action or Event to be performed, expected output and whether the Test Case has achieved the desired Output(Yes No).

Basically Test cases are based on the Test Plan, which includes each module and what to be tested in each module. Further each action in the module is further divided into testable components from where the Test Cases are derived.

Since the test case handles a single event at a time normally, as long as it reflects its relation to the Test plan, it can be called as a good test case. It does not matter whether the event passes or fails, as long as the component to be tested is addressed and can be related to in the Test Plan, the Test Case can be called a good Test Case.

SECURITY Testing is CARRIED out in order to find out how well the system can PROTECT itself from unauthorized access, hacking – cracking, any code damage ETC. which deals with the code of application. This type of testing needs SOPHISTICATED testing techniques.

Security Testing is carried out in order to find out how well the system can protect itself from unauthorized access, hacking – cracking, any code damage etc. which deals with the code of application. This type of testing needs sophisticated testing techniques.

No software application can be written in a CONTINUOUS mode of coding, at some point we need to branch out the code in order to perform a particular functionality. Branch coverage testing HELPS in VALIDATING of all the BRANCHES in the code and making sure that no branching LEADS to abnormal behavior of the application.

No software application can be written in a continuous mode of coding, at some point we need to branch out the code in order to perform a particular functionality. Branch coverage testing helps in validating of all the branches in the code and making sure that no branching leads to abnormal behavior of the application.

Domain testing is the most frequently described test technique. Some authors write only about domain testing when they write about test DESIGN. The basic notion is that you take the huge SPACE of possible TESTS of an individual variable and subdivide it into SUBSETS that are (in some way) EQUIVALENT. Then you test a representative from each subset.

Domain testing is the most frequently described test technique. Some authors write only about domain testing when they write about test design. The basic notion is that you take the huge space of possible tests of an individual variable and subdivide it into subsets that are (in some way) equivalent. Then you test a representative from each subset.

This is the very basic REQUIREMENT to START with the testing phase. We should have the test cases for testing any system. test cases is written based on the scenarios you have to test the system. Test cases GIVES us the assurance that FLOWS are working FINE or not based on the status of the test case. If the status of some test cases are failed meaning some flows are not working fine and there is bug in the system that needs to be fixed. If the status of the test cases are passed meaning flow is working as expected and system is behaving as per the requirement.

This is the very basic requirement to start with the testing phase. We should have the test cases for testing any system. test cases is written based on the scenarios you have to test the system. Test cases gives us the assurance that flows are working fine or not based on the status of the test case. If the status of some test cases are failed meaning some flows are not working fine and there is bug in the system that needs to be fixed. If the status of the test cases are passed meaning flow is working as expected and system is behaving as per the requirement.

Feature Ref No.: Login page

Sub feature No.: N/A

Test case id: TC_01

Functionality: Login

Steps Description: Enter the valid user name and password

Pre condition: Application must ACCEPT the user name and

password

INPUT Criteria: username: abc, Password: ***

Expected RESULT: Login user page should open with all its

content

Severity: C1: High, C2: Normal, C3: LOW

Observed Result: Application user page should open with all

its content

Status: Pass

Remarks: Done

Feature Ref No.: Login page

Sub feature No.: N/A

Test case id: TC_01

Functionality: Login

Steps Description: Enter the valid user name and password

Pre condition: Application must accept the user name and

password

Input Criteria: username: abc, Password: ***

Expected Result: Login user page should open with all its

content

Severity: C1: High, C2: Normal, C3: Low

Observed Result: Application user page should open with all

its content

Status: Pass

Remarks: Done

• ENTER the required data and CLICK the start BUTTON if it fails then it should come out and get restarts and Log=1;
• Enter the required data and click the start button if it fails then it should come out and get restarts and Log=1+1;
• Enter the required data and click the start button if it fails then it should come out and get restarts and Log=2+1;
• If log =3 then quit.

There are BASICALLY two types of test cases:

1. POSITIVE test cases

2. Negative Test cases

• Positive test cases are MEANT to test for which the application is made(functionality or the requirements).
• Negative test cases are meant to test for the which the application is not made.

There are basically two types of test cases:

1. Positive test cases

2. Negative Test cases

• Requirements Traceability Matrix
• Project NAME
• Requirements Traceability Matrix
• Unique No.
• Requirement
• SOURCE of Requirement
• SOFTWARE Reqs. Spec / Functional Req. Doc.
• Design Spec.
• Program MODULE
• Test Spec.
• Test CASE(s)
• Successful Test Verification
• Modification of Requirement
• Remarks

Test case is a detailed PROCEDURE that fully test a features or an aspect of a feature.

It describes how to perform a particular test. you need to develop a test case for each test LISTED in the test plan.

A test case includes:

• The PURPOSE of the test.
• Special hardware requirements, such as a MODEM.
• Special software requirements, such as a tool.
• Specific setup or configuration requirements.
• A description of how to perform the test.
• The expected results or success criteria for the test.

Test case is a detailed procedure that fully test a features or an aspect of a feature.

It describes how to perform a particular test. you need to develop a test case for each test listed in the test plan.

A test case includes:

1. check it can properly contain liquid and not LEAKED.
2. TEST that its size and shape as per user REQUIREMENT or not.
3. test its color as per user requirement or not.
4. test its material as per user requirement.
5. test it with maximum hot/cold and minimum hot/cold liquid.
6. check its strength that whether it can be BROKEN easily.
7. check its with heat and cold environment.
8. put it in front of direct sun light for hours.