Test Cases Interview Questions And Answers

for cup
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 fron of direct sun light for hours.

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.

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

TestCase ID : Tc_ 01

Test Purpose : For All the users logging form Loginwindow.It
consists Username and Password fields

Testprocedure : If User enter valid username with alpha-
numeric,password

Expected Result :Login window access

Actual Result :same

Pass/FailCriteria : Test pass

Remarks :No

Tc_02
If user enter invalid username with symbols like
*,&,./?,valid password

Expect Result : Login window opened

Actual result : Login does\'t access.it displays error msg

Criteria : Test case failed

Remarks : There is error msg displays.like enter valid user name

There are basically two types of test cases:

1. Positive test cases
2. Negative Test cases

-Positive test cases sre 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.

1. verify job should be executed for 2 hours validly executed( time gap we will calculate from previous job) job which was recent from the if not error message

There are two ways to test a stored procedure.

1)Black box testing: The Result Set should be checked if the
desired output is returned by SQL command.

2)Performance Testing: Stored Procedures are created to
avoid compiling it again and again. hence, testing should be
done to check if stored procedures are reducing CPU load and
network traffic.

1) Enter the required data and click the start button if it
fails then it should come out and get restarts and Log=1;

2) Enter the required data and click the start button if it
fails then it should come out and get restarts and Log=1+1;

3) Enter the required data and click the start button if it
fails then it should come out and get restarts and Log=2+1;

4) If log =3 then quit.

otherwise it should allow the user to perform the job.

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

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.

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.

Scenario tests are realistic, credible and motivating to
stakeholders, challenging for the program and easy to
evaluate for the tester. They provide meaningful combination
of functions and variables rather than the more artificial
combination you get with domain testing or combinatorial
test design.

In this type of testing the code is executed in such a
manner that every statement of the application is executed
at least once. It helps in assuring that all the statements
execute without any side effect.

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.

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.

A kind of testing in which, the application is tested for
the code that was modified after fixing a particular
bug/defect. It also helps in finding out which code and
which strategy of coding can help in developing the
functionality effectively.

Unit Testing is a testing done to check if the new code is working properly before delivering the build to testing team

Integrating testing is testing done when we move from one screen to an other screen or when two integrated modules are tested.
Acceptance testing is done when the product is delivered to the customer for him to accept.

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

smoke testing is tsting the most important functionality without going much deep into it when there's a new application delivered to testing team.

system testing is testing done on a completely integrated system to know it's compliance with the requirement.

Load testing is done to know if the application can work normally under the defined number of user and if the response is alright even under that load


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.

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

sanity testing is done after a new build to know if the important features are working propely .

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

monkey testing is something thatu do to test without following any document and some random unusal testing

gray box testing is the combination of unit testing and balck box testing

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

glass box testing is a structural testing where the test is derived by directly seeing the code.

dynamic testing is nothing but the black box testing itself.like testing a functionality by giving input and expect a output ..

compatability testing is done on differnt browsers to see if the response is same or if doesn't load properly.

concurrency testing is done to see if two users use the application parallely how tha application responds and how the data is handled.

component testing is same as unit testing except for stubs and stimulators removed.

adhoc testing is a negative tsting, testing done with an unwexpected situation or that 's not there in the requirement documents

agile testing -testing usiong the agile model.

Transaction testing: Transaction testing generally refers to the testing of individual loans and is also known as
account testing, account sampling, or transaction-level testing.

Syntax testing: Syntax testing is a static,black box testing technique for protocol implementations and for testing command driven softeware and similar application.

domain testing:it is a white box testing method and to check values taken by a variable, a condition, or an index, and to prove that they are outside the specified or valid range. It also contains checking that the program acepts only valid input , because it is unlikely to get reasonable results if idiocy has been entered. Colloquially, this part can be called ``garbage in -- garbage out'' testing.

logic testing:Logic-based testers design tests from logical expressions that appear in soft-ware artifacts such as source code, design models, and requirements speci-
cations

state testing:is a load testing type apporch and with this testing great flexibility in dealing with common system test problems: limited access to the system test environment, unstable software, or changing operational conditions. Because each test case verifies correct execution on a path from the idle state to the software state under test, our method does not require the continuous execution of all test cases.