Question { 5320 }

What is Test harness?

Answer

When you are writing test cases , whether they are unit
tests, tests for test-driven development, regression tests,
or any other kind, there are some functions you will find
yourself doing each time. These include the basics of an
application, a mechanism for launching tests, and a way to
report results. You could write these functions each time
you start testing a new feature or you could write them once
and utilize them every time. A test harness, at its most
simple, is just that—a system to handle the elements you’ll
repeat each time you write a test.

The typical objectives of a test harness are to:



The test harness should incluse the following capabilities:-
* A standard way to specify setup (i.e., creating an
artificial runtime environment) and cleanupAutomate the
testing process.
* A method for selecting individual tests to run, or all
tests.
* A means of analyzing output for expected (or
unexpected) results.
* A standardized form of failure reporting.

Question { 8054 }

What is the difference between functional test cases and
business test cases?

Answer

1.Functional Test cases are part of 80% of System test cases
where as Business test cases are also called as UAT test cases.

2.In Functional Test cases it describes about the
functionality of a particular screen matching with the SRS
where as in Business test cases describes about the Complete
business scenario for the entire application matching with
the BRS.

3.Functional test cases are concerned about external
behaviour of software e.g. input is properly accepted,
output is correctly produced and integrity of external
information is maintained. Test cases are based on high
level description of software requirement. In this approach
of testing, tester sees application as a black box means
tester is unawared and unconcerned about internal structure
of program.
where as in Business test cases are concerned about the
behavior of the entire business needs e.g. a particular
desired client business scenario is able to complete or not.

Question { 5096 }

I need a brief decsrpition on How to test borwser
compatabilty and O.S compatibity?
Wat are the techniques to test?

TIA

Answer

compatibility testing: Testing whether the system is
compatible with other systems( can be OS or browser) with
which it should communicate.

In your scenario follow these permutation and combination
level here

Application OS Browser pass/fail

XYZ app. Win98 I.E. ?

XYZ app. WinXP I.E. ?

XYZ app. Linux I.E. ?

XYZ app. Unix I.E. ?

XYZ app. win 98 Mozilla ?

XYZ app. Win XP Mozilla ?

XYZ app. Linux Mozilla ?

XYZ app. Unix Mozilla ?

In the same way test for Opera, Netscape , according to
clients requested OS and Browser. Here everytime the
application is tested on different browser on different
Operating system.

Question { 5351 }

We r developing one Web Site for construction company. In
that Web site we have different option like About Us,Contact
Us,Home,Sites,Site Map,Search Etc........ and front page of
that web application contains 6 different pictures means
single page contain 6 pics etc... write Test plan ,Test
Scenarios,Test Case ....Plz answer this question ASAP

Answer

If you need those you have to prepare of yourself. All
interview .com is supporting for queries but not for doing
some work. If you have any issues which you come across do
ask here.
Now for generating test plan do refer to IEEE 829 format
which you can get it when you google it.

Test Scenario--> since you know what the application is,
you can generate test scenario rather than other who
doesn;t know what your application does.

Test Cases---> depending upon the scenario generate test
cases of your own. The format of test cases is

Test Case name, Subject, Description, Design, Status, Step
No., Step Description, Expected result, Actual result.

Question { ABC, 14531 }

Please give an example of White box Testing?

Answer

Whit Box Testing:- It is done by the developers to check the
code to which they have written.
In white box testing we do the following testing techniques

1.Statement Testing.
2. Loop Testing.
3. Path Testing.
4. Branch Testing.
5. Mutation Testing.

In Statement Testing we check all whether all the statements
are given in a correct format and in a meaningful format.
In Loop testing we check whether the assigned loop is
terminating properly in the code part.
In Path testing each and every code has some path to flow
one path goes in one functionality and other path goes to
other functionality so here we need to check whether the
path flow is moving properly or not.
In Branch testing we check how many branches are there in
the code all the branches are moving properly
IN Mutation testing we check the standard of code like for
the working part of code remove some lines and then run the
code here we should get an error message related to the
removed lines of code - to justify whether the code is
working properly or not.


All these things need to tested by developers for there own
code before they release to QA team.

Question { Accenture, 14321 }

Hi All,
I am new in testing field. I got an interview and the
question was asked-
What would be your high level test case on the following
scenario. There are 2 fields one is SCORE and other is
GRADE and there is a go button. Scenario is If score is 90-
100 then grade should be A, if Score is 80-90 then B, if 70-
80 then C Else F.
So I told that -
I will check Boundary values by giving max +1 and min-1
values.
I will check the functionality is working as per the
requirement or not.
I will include + and - testing.
But seems like my answer was not correct, obviously because
I don't have much experience. So plz provide me the best
answer of this Q ?
Thanks in advance.
Preeti

Answer

Hi Preeti whenever you come across such questions in
interview we need to draw a flowchat for the asked scenario
and then decide how many High level test cases can we come
across, we have some topics which covers how many test cases
can be written for each and every flow , this is not an
ordinary question this is the question which they ask for
certification level.

Here is the flow for your answer


_________
| start |
|_______|
|
_________
| Score |
|_______|
|
/ \
/ \ Yes ________
/ 90- \ _____________ | "A" |___
\100 / |_______| |
\ / |
\ / |
| |
| No |
| |
/ \ |
/ \ Yes ________ |
/ 80- \ _____________ | "B" |___|
\ 90 / |_______| |
\ / |
\ / |
| |
|No |
| |
/ \ |
/ \ ________ |
/ 70- \ Yes__________ | "C" |___|
\ 80 / |_______| |
\ / |
\ / |
| |
|No |
____|____ |
| "F" | |
|________| |
| |
____|____ |
| End |___________________________|
|________|

The above flowgraph explains the scenario which you have said
Now obverse that from this scenario we can see that if
90-100 condition pass we get Grade "A"
if 80-90 condition pass we get Grade "B"
if 70-80 condition pass we get Grade "C"
else we can see "F".

So if we check then there wil be exactly "4" High level test
cases. I need to leave now I will explain in other time
continuine this answer.

Question { IBM, 5137 }

can u explain me v-model?I told him we will do parallely
both devolpment and testing .
frs------------useraccepatance testing
\ /
srs system testing
\ /
HLD integration testing
\ /
LLD--------------------- unit testing
\ /
CODING

he asked me how ur frs is done parallel with useracceptence
testing and srs is done parallel to system testing and HLD
IS done parallel to integration testing and LLD is done
parallel to unit testing.Give me a clear clarification for
it?

Answer

BUssiness Requirements(BR)- ----------> User Acceptence Testing
\ /
System Requirements(SRS)---------------> System Testing
\ /
High Level Design(HLD)--------------> System
Integratioon Testing
\ /
Low Level Design(LLD)--------> Component Integration Testing
\ /
Coding ----------> Unit Testing
\ /
\ /

\ /
\/
Build


V Model is a popular Software development model. It large
number of resources to implement.
In v model every development stage will have corresponding
testing stage.
Here test will be prepared in parallel with development phases.
i.e
After receiving the business requirements are prepared
then testing team will develop User acceptence Testcases.
But these testcases will be executed and the end of the project.

Here Business Requirements are very abstract in nature and
it talks just about What user/customer actually needs.
System Requirement Specifications will be prepared From
Business Requirements specifications.
SRS will be more elaborated then the Business requirements.
SRS tell what are system features need to be developed.
After seeing SRS Document Testing People will start
preparing System Functional Test cases.

After receiving High level Design Doc,Testing people will
prepare the System Integration Test cases.
After seeing Low level Design doc,Development team will will
prepare the Component integration Test cases.
After coding development team will prepare uint test cases
and executes the unit test on the each individual unit or
function.
Thus there is a mapping between the each development phase
with testing.

Question { 4391 }

Hello! can anyone explain IN DETAILS what is API???
thank you!

Answer

A formalized set of software calls and routines that can be
referenced by an application program in order to access
supporting system or network services.

Question { Cognizant, 6342 }

What is the main use of the quality center comparing to the
excel sheet?

Answer

The main advantages are

1. we can map the requirements to the test cases to check
if we have covered generating test cases for each and every
requirement which we cannot map in excel sheet.

2. Can upload test cases and docs very easily.

3. When bug found during execution we can easily know which
line it has failed with full details we can even take
snapshot of the bug easily which cannot be happened in excel
sheet.

4. N no. of users can use this

5. We can check the % of test cases executed and which are
not which is not possible using excel sheet that doesn;t
display any % of runned test cases.

6. We can see chart representation for the executed test
cases or bugs which by using excel sheet cannot prepare char
representation.


Hope this might give you some idea.

Question { 7289 }

What is the difference between Business Requirement and
functional Requirement

Answer

Requirement(BRS):-
BRS- business requirements specification. Business
analyst will interact with the client and will form BRS
document,
It contains
1.scope of the project
2.business rules
3.client requirements in depth.

Initially client will give the req's in their own format
then it will be converted in to Standard format( which we
call as Specification) by which s/w people can understand.
In BRS the req's are defined in general format. where as in
SRS ,the req's will be divided in to modules and each module
contains How many interfaces and screens it can have.
SRS:-
Based on BRS system analyst will form SRS document,
it contains
1. System requirements along with hardware requirements
2. Functionality to be developed and
3. what is input
4. what is output
5. what is front end
6. what is back end
7. what are the technologies
8. what r processes how they will interact.

based on sRS document design will be generated.


SRS is a Software /System Requirement specification,it is a
MS word doc. which defines the complete business
functionalities of the particular application
SRS designed by System Anallyst

Question { Samsung, 17319 }

How do we measure quality of testing? What are parameter of
this?

Answer

This can be difficult to determine. Many modern software
applications are so complex, and run in such an
interdependent environment, that Measuring Quality of
testing can never be said as 100%. Common factors in
deciding when we can measure the quality of testing is as below

1. Stability of the application.
2. Useful testing addresses important product risks and are
solved.
3.Test cases completed with max.percentage passed
4. Test budget depleted - Coverage of
code/functionality/requirements reaches a specified point
5. Bug rate falls below a certain level
6. Beta or alpha testing period ends successfully with
client satisfaction.

I think this would clarifiy your doubts.

Question { 5650 }

What is the difference bet white box testing and black box
testing.pls give me an example

Answer

White Box Testing:- White box testing is based on knowledge
of the internal logic of an application's code. DIfferent
test that take place here are
1. coverage of code statements
2. Branch testing
3. Path Tesitng
4. Condition checking testing.
5. Mutation Testing.

Both are done by Test Engineers but only difference is The
Tester who does Black Box Testing do have the knowledge of
coding part usually we take one of the developers as White
Box Test engineer.


Black Box Testing:- Black box testing is functional testing,
not based on any knowledge of internal software design or
code. Black box testing is based on requirements and
functionality.
Different test that take place here are

1.Boundary value analysis and Equivalence testing
2. Error Guessing
3. Error Handling
4. Compactability testing
5. Parallel testing
6. Configuration Testing.

Apart from these we have lot.

Question { 5650 }

What is the difference bet white box testing and black box
testing.pls give me an example

Answer

Black Box Testing:- Black Box Testing is a System Testing.
Here we check the complete functionality of the application.
Here the tester does not examine the programming code and
does not need the knowledge of any coding standards. Here he
enters an input and check whether we are able to get the
exact output irrespective of what is happening in the code.
Here we have functional testing and non-functional testing.
Again both are of different concepts.


White Box Testing:- White Box Testing is non-system
testing. Here the tester should have the knowledge of coding
standards. Here we should review the entire coding part like
we should go through the statement coverage testing, branch
testing and loop testing, mean to say that we have to check
the complete coding standards and mainly here we do Mutation
testing (like we make some changes to the existing code and
run the code and check whether we are able to get any error
or not). This again has lot of subject to learn, can’t be
described but you have to refer to the books to get the
complete knowledge on it. For more clarification if you have
the book called “Art of Software testing” it will make u
clear on these topics.

Question { 8380 }

Why you think tester is more important for good quality of
the product?

Answer

If you are already a tester / QA you should now this basic
thing right?

Any how let me clarify it.

Tester / QA is appointed to maintain the quality of the
product. For this QA should know the entire end -to- end of
the developing project in hand, and when they try to keep
the quality of the product they come across some kind of
disturbance which is nothing but we terminate as Bug,
Developers resolve it and fix the bug by fixing it QA does
re-testing and regression testing appropriately and thus
they keep track of all the Bug which come across of blocking
the quality of product. So in this way QA makes a major step
in maintain the quality of the product.
Quality of product stands with different issues
1. Usability issues
2. Performance and storage issue.
3. Functionality issue
4. COmpactibility issues too.

These are some of the part of quality of the product which
test engineer does which is divided into different levels
which we call it as STLC ( Software Testing Life Cycle).

Hope this might clarify your doubts.

Question { 7592 }

Which test cases are first written white boxes or black box?

Answer

It is written simultaneously at the design phase by two different groups. One team will be generating functional test cases ( which we call as behavioural or black box) and other team will be generating structural( which we call it as white box). But first structural test cases are executed and then given to testing team to execute the functional test cases.