Question { 3951 }

If tester had written test cases for application, then in
next build if same features are modified with some changes.
Then Should I have to write test cases for the same
features to verify new expected results.OR What should I do?

Answer

Yes if there are some slight enhancement we do have to
modify the previous test cases and write new test cases if
the functionality changes.
rest you can utilize or execute the same old test cases
which will useful to you.

Question { 4591 }

Should Tester have to write separate test cases document
for Functional testing, UI testing, Regression Testing,
Stress testing etc....?

Answer

No need to write test case for Regression or stress testing.
it will not be of use.

you will be writing test cases like


1. integration test case
2.Functional Test case
3.Non-Functional Test cases( which include security,
performance and usability)
4.User Acceptance Test cases( end to end scenario).

Validation test case:- Here all the above stated techniques
of test cases fall under validation test cases itself, there
is no seperate test case for validation, when we execute all
the above test cases we can conclude we have done the entire
validation too.

Verificatin test cases:- after writing the entire test cases
there will be some dedicated people who review these test
cases to check whether these test cases written according to
the requirements or not, in such a case it is called
verification test case and when we are executing those test
cases it is called validation test cases.


In a simple way expected results are verification and
actual results are validation.


Integration test case:- here we execute test cases which
just tells about the connectivity from one module to other
module and integrating one application to other application
and how the application moves from parent node to child node
and vice versa.

Functional Test case:- Here we execute test cases which
tells about the functionality of the application and talks
about the desired output to be seen. internally we have
different type of test cases when we write here like range,
output values , BVA, ECP and so on. We give input and expect
some output according to the SRS.Here we check individual
module completely by checking each and every tab , text box,
buttons and so on.

Non-Functional Test case:- Test cases related to User
friendliness like font, image, color, how easy to navigate
etc, performance related, security related comes under here.

User Acceptance test case:- These test cases are cruical and
very important to client side people, because these test
case talks about there business and approach of the
application to complete a particular client task. which is
also called as End-End- Business scenario test case. Here we
won;t be doing testing related to UI, Functional or
Non-Functional, we talk about business and scenario which
the application is made for.


This might give you a small ideas for your question. If you
feel this is right do respond to me and if you feel a change
in it also do respond to me stating your contradiction to
it.. which will be helpful to me also.


Hey this might help you.

when you want to do regression testing if you execute all
the above test cases related to it then it is sufficient .
No need to write further or seperate test case.

Question { 2661 }

Whether the testing process followed in different model
will be same or will it vary?

Answer

It definately varies that is why we have the concept of TLC
( Testing LIfe Cycle).

FOr v-model one methodology
for iteration other methodology
for water fall other methodology
for agile differnet

each and every model as its own way of testing methodologies
but one thing is that testing aim is the same find as many
bugs you can and maintain that the application works good
and perfect

Question { Vistar Tech, 4327 }

How much experience do we have to become a QA?
What are the responsibilities of QA?

Answer

Yes we should be having some experience to handle QA position

we should work as test engineer where our primary role would
be uder analysis rather than finding defect, analysis in the
sense modifying the requirements, reviewing taking place and
handling process .

QA is verifiation proces oriented or defect prevention. it
mainly focus on process. Most of the verification part done
by QA and validation part done by QC.


If we are really good in these we can be QA in 5 yrs but
still there is no exact age experience required for this.

Should be through in handling process and maintaining the
standard.

Question { Maslin Technologies, 69829 }

Any body can write the test cases for Address field, Mobile
Number field & Landline Number field ?

Answer

Hi ALl,

a.Address Field:-1. it should not be a text box, infact it
should be a grid as it will accept more characters.
2. IT should accept characters, numbers and few special
characters like #,@,/,(,) and - only
# --->to be used for giving flat no. like #101,
@ --->if they are giving mail address,
/ --->and - if they go for door no.,
(,) --->for writing alias name like sameer (abdul).

3. Pin code should not be in grid box if it is there we
cannot validate it, so it is always advisable to have pin
code as next text box to validate because in for no. 2 we
have given validation to special characters which is always
advisable and we cannot validate here in pin code which will
be a mismatch. so always advisable to be as seperate text
box , you can view to more no. of application where pin box
will be seperate.

b Mobile and landline number field?
for these both we should have seperate individual text boxes.


Mobile Number:-1. it should strictly accept only
numericals.and numbers should not be less than 8 digits
because the universal code digits for mobile starts from 8
mandatory.
2. all the digits should not be zeros.

landline:- it should be of two text boxes one for code and
other for no.
and it should strictly accept numericals only. the country
no ( should be valid country no.) and landline no. should be
correct.


for these following points we have to create test cases.
I hope this might help you.

Question { 3347 }

In any application there are so many fields.
So tester have to test each field with Special chars.,
Alphabetic value, Alphanumeric value, Blank Space. etc.
I am testing with all these inputs but should I have to
consider these into test cases.
Because rather than these there many functionalities to
check.Please Guide me properly

Answer

The above answer is write but if we do so we have to
generate 1000 of test cases, but is not good practice.

Write one test cases for the above scenario and keep that
name as Field checking( name of the field).

Once written that test case. Now when you are executing the
test case execute that with all the above scenario values.
Means for the same test case give input value as Special
character for first time, give input value as Alphanumerical
for second time and so on depending upon the requirement.

But the input values entered should be noted down in the
excel sheet itself. for this add more column as input
value and enter the value for each column so that for the
same test case u can excute with multiple values.


This would save your time and all the input will be in one
place .

If anyone is having a better idea do share so that it would
be helpful.

Question { Tech Mahindra, 13964 }

What is white-box Integration Testing and its differences
between Black box-Integration testing?

Answer

Actually there is no concept of White-box integration
testing and black box- integration testing but we can keep
this in this scenario if it has to be explain ...like below

Integration testing techniques are

1. Top-Down
2. Bottom-up
3. sandwich / hybrid

and in integration we club one module to other module and
check the connectivity which is a functional technique, and
sometime if one module is ready and other module is not
ready to move to third module we take help of developers for
developing a small piece of code which we call it as stub
and driver. Stub and driver is a small link that connected
from one module to other module so it is called white box.

SInce we need both white box technique and black box
technique it is called Grey Box testing


Integration testing is a grey box.

Since we are using stub and drivers in integration we can
call it as white-box integration testing and
since we are using black box technique in integration we can
call it as black box integration testing.


Hope this will help you to understand

Question { Canon, 5382 }

Plese tell me What is V model how do u prepair documnet
using V model ?

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 { 5629 }

What is Alpha and beta testing and What is the diffrence
between Alpha and beta testing ?

Answer

Alpha testing and beta testing are done under UAT technique.

Alpha testing:-If the build is tested successfully with all
system testing technique and security testing they will
deploy that build in one the server located at developers
site. Once deployed in developers site ( company developed)
they start doing final round of testing to check that the
application is meeting the requirements and user
needs(Business) . SO testing done at developers environment
is called ALpha Testing.


Beta Testing:- Once the above ALpha testing is done they
will deploy this build in clients location on clients
machine which we call it as main production machine. Once
deployed there testing done with all business techniques.
Here in Beta testing all business related or few user come
and test the application and check whether they can complete
there own business. One the users satisfy then only it will
be lanched in market.

Question { 10116 }

What is penetration matrix ?

Answer

It's relatively a new term used recent times as many company
now a days are looking for security of the networks too.
Each and every company will have there own internal
terminology. we can call it as Security assessment also.

At its simplest, a penetration-test is the process of
actively evaluating your information security measures.The
information systems will be tested to find any security
issues, as opposed to a solely theoretical or paper-based audit.

The results of the assessment will then be documented in a
report, which should be presented at a debriefing session,
where questions can be answered and corrective strategies
can be freely discussed.

Question { Hydus, 4242 }

Is there any other tool like QC which we can get as open
source. the software should be able to write test cases,
store documentation, dashboard and bug report. If anyone can
suggest me it would be helpful.

Answer

Hey Ruchi thanks for the information regarding Jira, but TD
is not an Open source and TD doesn't have dashboard. QC is
nothing but dashboard added to TD.

Question { 6560 }

How test case is differ from test plan .give an suitable
example

Answer

Test cases will be written depending upon the test plan we
create because

Test plan has the following indexes like
(IEEE 829 Standard)

1. Test Plan Identifier
2. References
3. Introduction
4. Test Items
5. Software Risk Issues
6. Features to be Tested
7. Features not to be Tested
8. Approach
9. Item Pass/Fail Criteria
10. Suspension Criteria and Resumption Requirements
11. Test Deliverables
12. Remaining Test Tasks
13. Environmental Needs
14. Staffing and Training Needs
15. Responsibilities
16. Schedule
17. Planning Risks and Contingencies
18. Approvals
19. Glossary



Where Features to be tested, Features not to be tested, Item
pass/ fail criteria and approach. From these we can know
what would be the input to be given and what would be the
output we have to expect which is nothing but ( expected
results for the steps ). These form the baseline for test
cases where approach tells us what kind of techniques to be


1. Item pass/ fail criteria tells what would be the input to
be given and what would be the output to come which is
nothing but expected results for the steps designed.

2. Features to be tested and features not to be tested give
you an idea what all test cases to be written to all what
modules.

3. Approach and stratergy gives you and idea like what kind
of methodology the test cases should be and for what
methodology what kind of techniques to be used..

SO all these became a baseline to generate test cases , so
we can clearly say for generating test cases test plan
becomes the baseline..


If we are familiar with test plan and preparation of test
plan then it would be easy for all QA and QC people .

HOpe this might gives you the answer.

Question { 5994 }

1. Hai, if we are not having any SRS,BRS docs., how can we
prepare the test cases & how can we test the application ?
2. In this, is it possible to make 100% bug free.

Answer

I partially agree with preeti answers.(doesn;t mean I am
underestimating preeti comments, she is right form CMM level
point of view, think for companies which are start up or
middle level company).( Hope preeti can understand)

First of all let me give answer to question no. 2 As preeti
said which is true no software or application is 100% free
from bugs. We do come across lot of bugs when it is already
running or using,those bugs will be noted down and will
document it and solve it and release it as next version.
Because of this we do have lot of release and version
concept. So no application is 100% free from bugs.

NOw let me answer the 1st question which is realy a critical
question but the answer is

There are companies where development and testing done
without having BRS and SRS, it doesn;t mean that they are
stop developing the application?( as per preeti comments)

Whenever we are not having any kind of documentation from
ourside these are the points that can be useful to test

1. Analyse the application well and understand what the
application is trying to do.

2. Write down your understandale level in a word doc. like
what the application does, what each and every module is
handling and what are the tabs it has and its usage (
everything which you can write it).

3. Inform the other team members to follow the same
stratergy and collect all the documents.

4. Send this documentation to your superior( test manager,
project manger) and give them to confirm it with clients for
which the application is done or doing,Is this the
application should be and ask for confirmation before you
more forward.

5. Take the confirmation documentation from there and then
as usual generate design doc, test cases and rest of the
other activities which normal test engineer does.


IN one way we have to be act as QA, Bussiness Analayst role
. When you can do this well you can be a QA easily.

This is the processs most of the middle level company does.


Hope it might help you, If there are any other ways let me
know so that I can also learn it.

Question { IBM, 15832 }

What is diff between Agile SDLC and TDD SDLC? Kindly let me
know?

Answer

TDD ( Test Driven Development):-
1. It well supports unit tests and having programming
paradigm that is bit more flexible in regards to scope changes.

2. Having unit tests available will make our code more
maintainable over the long run is invaluable because we can
modify our code without fear such as when we are
adding/modifying functionality or refactoring.

3. It could be considered crucial when we have projects
where the scope is likely to change throughout the
development lifecycle like in the case where the functional
specifications are not clearly defined before we begin
producing code.


SDLC should be in the following way

1. As a first step, we'll define the interfaces out software
will adhere to.

2. Add a test
3. Run all tests and watch the new one fail (and the rest
succeed)
4. Modify our code to make the test succeed
5. Run all tests and watch them succeed
6. Refactor, if necessary
7. Run tests to ensure everything still works
8. Repeat

These are the steps we follow for TDD SDLC.


Agile SDLC:-
1. Agile aims to reduce risk by breaking projects into
small, time-limited modules or timeboxes ("iterations") with
each interation being approached like a small,
self-contained mini-project, each lasting only a few weeks.

2. Each iteration has it own self-contained stages of
analysis, design, production, testing and documentation.

3. In theory, a new software release could be done at the
end of each iteration, but in practice the progress made in
one iteration may not be worth a release and it will be
carried over and incorporated into the next iteration.

4. The project's priorities, direction and progress are
re-evaluated at the end of each iteration.

Hope this might give you all an idea.

Question { 5134 }

I have sent a mail through gmail.But it is not showing in
the Sent mail option.Can any one tell me the defect
description for this(asked for an interview)?

Answer

Before anyone enters a bug for this desription certain
things need to be observed first.

1. Did they get the confirmation message " sent
successfully", if so check the database and see whether it
is sent successfully.

2. Check the front end application and check whether we can
see the message in sent mail if not visible check the
message in database and view whether we can see the message
saved in sent table or not.

3. if the message do exist in database of sent mail table
then it might be the problem of getting the data from
database and displaying it to the front-end.

4. Might the problem that it is not saving in the sent mail
table properly.


These are some of the issues that might happen and we have
more too, so do check for these constraints and then report
them correctly accordingly so that they come to know we have
tested in a rightful manner.


Might help you ... if there are any other issues let me know
, might be useful to me aslo.