Question { Crea, 5741 }

Testing mainly in Verification or Validation ?

Answer

-Verification deals with whether the product is right or not??
-While validation deals with whether its a right product or
not that means whether it can give solution to every
problem or not.
-Validation also deals as whether the product is fit for use
or not.

Question { Crea, 5741 }

Testing mainly in Verification or Validation ?

Answer

Validation: The process of evaluating software at the end of
the software development process to ensure compliance with
software requirements. It is actual testing of the application.

1. Am I building the right product.

2. Determining if the system complies with the requirements
and performs functions for which it is intended and meets
the organization’s goals and user needs. It is traditional
and is performed at the end of the project.


Verification: The process of determining whether of not the
products of a given phase of the software development cycle
meet the implementation steps and can be traced to the
incoming objectives established during the previous phase.

Verification process helps in detecting defects early, and
preventing their leakage downstream. Thus, the higher cost
of later detection and rework is eliminated. It includes:

1. Am I building the product right.

Question { Crea, 5077 }

What is the responsibility of programmers vs QA?

Answer

Responsibility of a programmer
------------------------------
1.Programmer develops the functionality of a application

2.Write the code

3.Doesn't need to have business knowledge(can be pure
technical)

Responsibility of a QA
----------------------
1.Helps in improving the quality of a application

2.Understand the needs of user as well as client

Question { 7113 }

Testing Engineer having Software Programming knowledge so
Which type of testing will be done.
1.Adhoc testing
2.random testing
3. functional testing
4. monkey testing

Answer

I think answer should be functional testing.

Because monkey testing and random testing is done when the
user/tester doesn't have any knowledge about the
functionality of the application.

They put random values move here and there to go through
that app.

And under ADHOC-TESTING these are coming.

Question { 6499 }

what are the definitions of smoke , sanity and dry run
testing ?

Answer

SMOKE TESTING:
--------------
Smoke testing originated in the hardware testing
practice of turning on a new piece of hardware for the first
time and considering it a success if it does not catch fire
and smoke. In software industry, smoke testing is a shallow
and wide approach whereby all areas of the application
without getting into too deep, is tested.
A smoke test is scripted, either using a written set of
tests or an automated test.

SANITY TESTING:
--------------
A sanity test is a narrow regression test that focuses
on one or a few areas of functionality. Sanity testing is
usually narrow and deep.
A sanity test is usually unscripted.

Question { 6574 }

what is soak testing

Answer

Soak testing is running a system at high levels of load for
prolonged periods of time. A soak test would normally
execute several times more transactions in an entire day (or
night) than would be expected in a busy day, to identify any
performance problems that appear after a large number of
transactions have been executed.

Question { Hewitt, 8547 }

12. What is the configuration management?

Answer

Configuration management (CM) is the detailed recording and
updating of information that describes an enterprise's
hardware and software. Such information typically includes
the versions and updates that have been applied to
installed software packages and the locations and network
addresses of hardware devices. Special configuration
management software is available. When a system needs a
hardware or software upgrade, a computer technician can
accesses the configuration management program and database
to see what is currently installed. The technician can then
make a more informed decision about the upgrade needed

Question { Hewitt, 10403 }

10.What is stub?

Answer

Stub is dummy module which is used when a module is already
developed and to test that module we need another module
for interfacing.

-stub is being called while driver calls a module.

Question { Zenith, 6321 }

what is test case review?

Answer

The main reason of the reviewing test cases: increase test
coverage and therefore product quality.

LEVEL'S of TEST CASE REVIEW
---------------------------
1.Defect Prevention

2.Assurance having traceability between requirement and test
cases
3.separation of developer code and test cases

Question { 6863 }

What is kick-off meeting? Why is it optional?

Answer

1.Kick-off meeting is a step among the process of formal review.
2.A kick-off meeting is typically a workshop type meeting.
It generally include several activities such as a project
charter, a business plan review, team building exercises, a
team charter, risk analysis...
3.if in the everybody is a professional then meeting is
optional.

Question { 7923 }

what is scenario????

Answer

Test scenario is a high level description of business
requirements,which is later decomposed into set of test cases.

However test scenarios are different from test cases because
they usually have several steps whereas test cases are
single steps.

Question { 12065 }

What is exploratory testing?

Answer

In general,we all have versatile nature like

FOR EX:we all know writing,reading,walking but lawyers need
to be expert in reading.thats it.

Exploratory testing is nothing but testing and simultaneously
learning.

It is also called as "ad-hoc testing".

Question { 3578 }

what is the difference between development and testing

Answer

A programmer puts the software together and delivers it to
the next person in the chain to try it. They will report
back to the programmer and issues and/or problems which were
observed.
This is whole process.

DEVELOPER+TESTER=SUCCESSFUL PROJECT

Question { 3996 }

what is the difference between quality and testing ?

Answer

Hi All,


-Quality means only and only "meeting specification" nothing
else.

-what a user want??if he is getting everything then he will
say good quality.

-Quality leads to a brand not the vice verse.

-Testing doesn't mean quality improvement.

-Testing means exercising your brain a little bit to
examine a product..In turn the result is improvement of
quality.

SO QUALITY IS NOT THE AIM OF TESTING,BUT OUTPUT LEADS TO
IMPROVEMENT.

Thanks

Question { BT, 8124 }

What are the Risks involved while testing?

Answer

The following are the major risks involved in Software Testing.

1) Unclear or ambiguous Requirements

2) Lack of time

3) Lack of Resources (SW,HW and Human)

4) Lack of Documents(BRS,SRS or Use Cases)

5) Lack of knowledge on project domain.