[slinkanand]

1)What is Test Efficiency and what is the metric used for the same?
Ans) if it is efficiency of the testing team is there a formula to find it
a/a+b(the defect removal)
a: the defects found by tester
b:defects found by user

2) why do u like testing?.. y did u select this domain?. what do u like most in testing job?. how do u satisfy with this job?.

Ans) I love testing as its a destructive process to make the product better, developers are constructing it but not sure about the quality so we need to test and verify if this works fine.
testing means 'trust, but verify', more challenges , for exploration so i selected testing.
The simple logic for selecting testing as domain is..... Whatever product/project u develops needs to be tested before getting into market. It plays a major role in Quality of product/project. So testers r the responsible persons for delivering Quality product/project. So, I want to be in the project where quality of the product/project is delivered.

It's a innovative technology. quality gets through testing only. writing test cases and involving in test plan every day is a challenge to me

One reason I particularly enjoy in this filed and the challenges that go along with it, is the opportunity to feel responsible (product or projects worth in the market depends on your testing skills and your earnest efforts while testing).

3) Can any one tell what are the components of test cases.
Ans) Firstly we should know that why test cases is written??? . Ans is that test cases contains whole steps that a tester have done to test the object. it contains test input actions and results(Exp/Actual), Entry criteria of testing and exit criteria.
normally tester follows thisformat:
Project Module Functional specification prepared by review by
Entry Criteria Exit criteria
1: Test case ID
2: Step No:
3: Steps:
4: Expected Results:
5: Actual Results:

q)Can anyone tell me what is usability testing and in which stage it should be done ?
It is user interface testing that means our application following MS 6 rules r not and
Spell Check, Meaningful error messages,Graphic check,accuerency of data from the database as a result of user input and meaningful help messages.



q) what is the diffrence between regression testing and retesting?in which stage a tester undertakes regression testing and retesting? is both of them same
Regression testing is done on modified build i.e., build is arrived with changes or any bug is fixed.
Retesting is done on same build. this is to ensure that all major functionality is tested and nothing else missed.
They r not same at all!!!!!
q)When a build arrives ,what is the preliminery testing we go for
Normally when build arrives tester will go for sanity testing. i.e., whether the build is stable enough, all the images/links are opening......
First thing to do, which is all that was asked for in the question, is to run the Test/QA acceptance test, or this may also be referred to as the smoke test and also other names. But the essence of the TAT or the BAT (Build Acceptance Test as we call it) is to install the application to see if it will install properly, then do a few functional tests to see if the application is stable enough to start testing. If it isn't, we reject it.
q)Is functional testing a part of system testing?
System testing covers functional and non-functional testings
functional testing: functioality testing,input domain testing...
non-functional: performance,security,compatability.......

q)What is test procedure?
Ans) Test Procedure is a document which describes how a tester will actually run the test. This would include the physical set up, starting point of the test, and the steps that need to be followed.

Based on the fact that it contains steps to be followed it could equate to a test script, many people however use Test Script for automated testing and other terminology for manual testing.

q)What are the disadvantages of overtesting?

Overtesting an applicationmean,trying to test each and every possible combination of functional flowswhich is never possible in this ideal world.
Most of the customers may not use all the features of the application(especailly if it is product rather being project)and thus wewill wasting our resources unnecessarily on those low priority aspects of the product. Rather spending time onthese low priority features, if we concentrate on high priority/most frequently used features, that may yeild high productivity. Again, a point to stress here is, it is never possible to release a bug free application. But, by testing we can only minimize the cost of the bugs.


q)What happens to the test plan if the application has a functionality not mentioned in the requirements?


It clearly represents the communication gap between PM(Project Management)/Dev team and QA teams.

In case of such situations, first try to understand the new functionality that is added ( by contacting dev or PM POC's) and then know what is the business requirement for it and get ajustification from them.Then QA should be able to guess what will be its impact on the over all functionality. If it impacts the functionality or changes the complete functionality, then the QA should modify their scripts accordingly. If the new functionality does not have any impact on the functinality then there won't be any chages. But, in real time, the situation will be, we have to uplift our scripts covering the new
features.

Q) Diff between Functional and Non-functional req?
Functional requirements = what shall your application do?
Non-functional requirements = how shall the functional requirements be fulfilled (e.g. in terms of performance, reliability, fault tolerance, ...)?
Q) Functional testing vs System testing

---

System test denotes what is being tested (as opposed to unit test or integration test). Function test denotes how something is being tested (behavioural or black box testing techniques as opposed to white/clear box testing).System testing normally will begin when you have a fully integrated system (or sub-system perhaps on large scale products) which is deemed ready for testing by whatever criteria you choose. You will likely use functional testing techniques to perform much of this system-level testing, perhaps augmented by other more code-aware testing techniques as needed.

QA questions—


Design FMEA or Failure Modes and Effects Analysis (FMEA) is methodology for analyzing potential reliability problems early in the development cycle where it is easier to take actions to overcome these issues, thereby enhancing reliability through design.

Benchmarking is the continuous process of measuring products, services and processes against the toughest competitors or those companies recognized as industry leaders

Benchmarking improves Customer satisfaction

Benchmarking considers your own organization as the one with industry Best Practices that lead to superior performance

PDCA Cycle is also called as Deming cycle
Deming’s theory for Management is also called as 14 point theory

Prevention Cost is a external failure cost

Cost of Rework is an Internal failure cost.

What does PDCA mean? PLAN DO CHECK ACT

Process: Following Quality Standards in the entire life cycle is also reffered to be a process

What is a change control board?

A change control board is personals responsible for handling the change in SDLC either it would be change to a document, client request or resource.
Eg: Change in client request the control board shall be the Project Manager/Functional head & Management Representative/QA

what is meant by version control?

To brief about version control, it is a mechanism of managing the versions of files in the project. For example let us take a file A prepared on a certain date by a person XX and the same file is modified by a person Y on the same date. There comes a question how it can be tracked? This is the place we apply version control tools like VSS, CVS which helps us to keep track of versions, modified person's name, time, comments.. if the data is lost by any chance version control tool helps us to recover the latest data from the repository

Change Request?


After releasing of first version of software , when user need some changes in previous version , then its called "change request"

What is Defect Rejection Ratio (DRR) and Defect Leakage Ratio (DLR)?


DRR = # of Defects Rejected/Tester to assess the tester performance
DRR = # of Defects Rejected/module to assess the module complexity
DRR = # of Defects Rejected/Team/Project to assess the team performance.
and
DLR = # of Defects uncovered/Tester
DLR = # of Defects uncovered/Module
DLR = # of Defects uncovered/Project
(Uncovered- Defects missed out by the testing team)

[das.testing]

Hi Anand,

Well done

Regards

Arun

[vanik]

thanks

[au123]

Hi Dude

What is this, I often find this in ur threads and some times get confunsed too.

[slinkanand]

Originally Posted by au123

Hi Dude

What is this, I often find this in ur threads and some times get confunsed too.

Ahem, what do u mean?

[naveen_p25]

Hi Anand,

You are doing a noble service with your contribution to this forum. I am requesting you please keep on posting your threads for the benefit of new faces in Testing.

1. what are MS 6 rules?
2. Please also send your answers for regular interview questions in testing?

[sridhar1047]

hey anad whats the major diffrence between a software test engineer and a QA guy?
in the sense that the work that they do.
do all companies have seperate testing and qa departments or can a testing guy do qa work and vice versa?

[raji6ft]

Hi Sridhar,
I beleive that the answer lies in the size of the organisation.I work for a middle level organisation and work as a Software Tester for a few projects and do the QA work for few other projects .We have a single department as such.

[sridhar230]

Fine thanks they are really good Nice collection

[abhi_dreamzat]

Hi anand ... Thanks for the posting ... it's very useful. anywys wht's u'r profession n location

[Afterlife]

gud one dude 10x