Question { 4125 }

What is Buddy testing?

Answer

Buddy means group of programmers and testers.

Lack of time and lack of test data test engineers grouped with developers to conduct test on application as early as possible this style of testing.

Question { 6640 }

What is meant by retesting? Is it similar to smoke/sanity
testing?

Answer

Retesting can't be a smoke/sanity testing. that's different.

Retesting:

Retesting simply means repeating a test case whereas when it comes to regression testing a plethora of cases open.

Retesting is testing the bugs are fixed or not which were reported.

Retesting means, testing the application with multiple inputs.

Question { 9486 }

what is agile model?

Answer

Agile testing is used whenever customer requirements are changing dynamically if we have no SRS, BRS but we have test cases does you execute the test cases blindly or do you follow any other process.

Question { MedUSA, 6609 }

What is backward compatibility testing?

Answer

Testing whether the system is compatible with other systems with which it should communicate.
Compatibility testing measures how well pages display on different clients.

For example: browsers, different browser version, different operating systems, and different machines.

At issue are the different implementations of HTML by the various browser manufacturers and the different machine platform display and rendering characteristics.

Also called browser compatibility testing and cross-browser testing.

Compatibility is a product feature and can have different levels of compliance.

Question { IBM, 8323 }

What are your salary expectations?

Answer

Weather you are a fresher or experience it doesn't matter.

You have to speak out very boldly, which is very important.

Because the person who have a quality of bold speech is a quality of LEADER SHIP.

Company really like you when you are very bold.

Question { IBM, 5513 }

What's an 'inspection'?

Answer

An inspection determines if the material or item is in proper quantity and condition, and if it conforms to the applicable or specified requirements.

Critical appraisal involving examination, measurement, testing, gauging, and comparison of materials or items.

Inspection is generally divided into three categories:

(1) Receiving inspection.
(2) In-process inspection.
(3) Final inspection.

A document that provides instructions on how an inspection of a product is to take place.

Inspection plans provide details about what characteristics must be tested in order to ensure the quality of the product, as well as specific metrics and measurements that must be achieved in order for the product to be judged in compliance with standards.

Question { Zensar, 6063 }

what are the levels in testing?
(Asked in Zensar Hyderabad today(17-1-12010))

Answer

software testing:

Software testing is an essential part of software development which is used to identify the correctness, completeness and quality of developed software.

Software testing is the process used to help identify the correctness, completeness, security & quality of developed computer software.

Its main objects are to detect error in software.

levels in testing:

1. Unit Testing.
2. Integration Testing.
3. System Testing.
4. Acceptance Testing.
5. Regression testing.

Unit Testing:

A unit is smallest testable piece of software.
– can be compiled, linked, loaded.
– e.g functions/procedures, classes, interfaces.
– normally done by programmer.
– Test cases written after coding.

Disadvantage:

– Test cases ‐written to suit programmer’s implementation.

Integration testing:

Test for correct interaction between system units.

systems ‐ built by merging existing libraries.

modules coded by different people.

Mainly tests the interfaces among units.

Bottom up integration testing.
-Use of drivers
Top down integration testing.
-Use of stubs

System Testing:

Test of overall interaction of components.

Find disparities between implementation and
specification.

Usually where most resources go to.

Involves – load, performance, reliability and security testing.

Acceptance Testing:

Demonstrates satisfaction of user.

Users are essential part of process.

Usually merged with System Testing.

Regression Testing:

On going process throughout testing life cycle.

New bug‐fix breaks previously tested units?

Perform regression test whenever program changes.

Done by test team and customer.

Done in simulated environment/real environment.

Question { Zensar, 6874 }

what is bug life cycle?
(Asked in Zensar Hyderabad today(17-1-12010))

Answer

Life Cycle of a Bug:

Given below are the stages of a bug life span. Test reports describe in detail the behavior of bug at each stage.

New:

This is the first stage of bug life cycle in which the tester reports a bug.

The presence of the bug becomes evident when the tester tries to run the newly developed application and it does not respond in an expected manner.

This bug is then send to the testing lead for approval.

Open:

When the bug is reported to the testing lead, he examines the bug by retesting the product.

If he finds that the bug is genuine, he approves it and changes its status to 'open'.

Assign:

Once the bug has been approved and found genuine by the testing lead, it is then send to the concerned software development team for its resolution.

It can be assigned to the team who created the software or it may be assigned to some specialized team.

After assigning the bug to the software team, the status of the bug is changed to 'assign'.

Test:

The team to which the bug has been assigned works on the removal of bug.

Once, they are finished with fixing the bug, it is sent back to the testing team for a retest.

However, before sending the bug back to the testing team, its status is changed to 'test' in the report.

Deferred:

If the development team changes the status of the bug to 'deferred', it means that the bug will be fixed in the next releases of the software.

There can be myriad reason why the software team may not consider fixing the bug urgently.

This includes lack of time, low impact of the bug or negligible potential of the bug to induce major changes in the normal functioning of the software.

Rejected:
Although, the testing lead might have approved the bug stating it as a genuine one, the software development team may not always agree.

Ultimately, it is the prerogative of the development team to decide if the bug is really genuine or not.

If they doubt the presence or impact of the bug, then they may change its status to 'rejected'.

Duplicate:

If the development team finds that the same bug has been repeated twice or there are two bugs which point to the same concept, then the status of one bug is changed to 'duplicate'.

In this case, fixing one bug automatically takes care of the other bug.

Verified:

If the software development team sends the fixed bug back for retesting, then the bug undergoes rigorous testing procedure again.

If at the end of the test, it is not found then its status is changed to 'verified.'

Reopened:

If the bug still exists, then its status is changed to 'reopened'.

The bug then traverses the entire of its life cycle once again.

Question { 6160 }

what is batch testing?

Answer

Batch testing is having a bunch of coded tests and running them all at once, whereas manual testing would be picking a test and running it individually.

It is almost always better to have batch tests, because that lets you validate builds with batch testing and easily to regression testing.

Batch testing is an integral part of Wild Country's quality system. It is a process in which one test is done simultaneously on multiple specimens.

Steps for Batch Testing:

1). Prepare Individual Tests and Run once.

2). Open Test batch Runner Tool and Form Batches.

3). Run or Execute Test Batches from Test Batch Runner.

Question { 4731 }

what is confirmation testing??

Answer

Confirmation testing is also known as re-testing.

Retesting is planned based for the defect fixes listed in Build Notes.

Retesting is carried out to verify defect fix / fixes.

Retesting is done to make sure that the tests cases which failed in last execution are passing after the defects against those failures are fixed.

Retesting involves executing test cases that were failed earlier.

Retesting always takes higher priority over Regression testing i.e., Regression testing is done after completing Retesting.

This is known as confirmation Testing or Re-testing.

Question { 5382 }

Would u provide the exact differences of test case and test
conditon 2)test case and use case 3)test suite and test
scenara

Answer

TEST CASE:

A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.

A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.

For every test case, we can identify +ve and -ve points.

Based on the criteria, we will write the test cases, if it is crucial process or screen.

We should check the screen, in all the boundary conditions.

USE CASE:

A simple flow between the end user and the system.

It contains pre conditions, post conditions, normal flows and exceptions.

It is done by Team Lead/Test Lead/Tester.

Test Scenario:

A name given to test case is called Test Scenario.

The test scenario is deal by the test Engineer.

Test Strategy:

Is a document, developed by the "Project manger" which contains what type of technique to follow and which module to test.

TEST PLAN:

Test plan is a document, developed by the test lead, which contains "what to test" "How to test" "When to test " and "Who to test " .

Question { 5535 }

what is soak testing

Answer

soak testing:

Soak Tests is also Known as Endurance Testing.

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 than would be expected in a busy day, to identify any performance problems that appear after a large number of transactions have been executed.

Also, it is possible that a system may ‘stop’ working after a certain number of transactions have been processed due to memory leaks or other defects.

Soak tests provide an opportunity to identify such defects, whereas load tests and stress tests may not find such problems due to their relatively short duration.

For example, in software testing, a system may behave exactly as expected when tested for 1 hour.

However, when it is tested for 3 hours, problems such as memory leaks cause the system to fail or behave randomly.

Soak testing falls under stress testing.

Question { 3359 }

I’ve heard that Zephyr, a test management tool saves the
trouble of sending weekly and monthly status reports. Is that
true?

Answer

Actually, it is not like that.. It depance upon the tool and the project..

Question { 14294 }

Explain pilot testing.

Answer

pilot testing:

Pilot Testing is a Testing Activity which resembles the Production Environment.

It is Done Exactly between UAT and Production Drop.

Few Users who simulate the Production environment to continue the Business Activity with the System.

They Will Check the Major Funtionality Of the System before going into production .This is Basically done to Avoid The highlevel Disasters.

Priority Of the Pilot Testing Is High and Issues Raised in Pilot Testing Has to be Fixed As Soon As Possible.

Pilot testing involves having a group of end users try the system prior to its full deployment in order to give feedback on IIS 5.0 features and functions.

The level of pilot testing you want to perform depends on the size and scope of your migration project.

For larger projects, a formal, carefully planned pilot is essential.

For any size project, its good to have selected end users test the system prior to full deployment.


The following are items to include in planning a pilot test:

1. Adequate training for participants.

2. A roll out plan for deploying the servers and preparing systems for the pilot.

3. Documentation of the installation process so you can improve it as more is learned.

4. A mechanism, such as a Web site or e-mail alias, for users to provide constant feedback to the design and testing teams.

5. Evaluation criteria for the pilot, including information about the number of users who were dissatisfied, the number of problems reported, the number of support calls and requests, and the resolution rate for problems.

Question { 4106 }

What are estimations? How do you estimate?

Answer

Estimations represent "Expectations of how a company will perform in the future".

Estimations arrive at their estimates and ratings by doing things like talking to company managements, a company’s customers and suppliers, evaluating relevant economic data, and using all of these things as the basis for making their forecasts.