FAQS

Q - What are test case formats widely use in web based testing?
A - Web based applications deal with live web portals. Hence the test cases can be broadly classified as - front end , back end, security testing cases, navigation based, field validations, database related cases. The test cases are written based on the functional specifications and wire-frames.


Q - How to prepare test case and test description for job application?
A - Actually the question seems to be vague,... see naukri is one of biggest job site globally and it has is own complex functionality normally a Test case is derived from a SRS (or) FRS basically and test description is always derived from a Test case. Test description is nothing but the steps which has to be followed for the TC what u wrote. And the TC is nothing which compares the expectation and the actual(outcome)result.


Q - What is the difference between Functional and Technical bugs? Give an example for each.?
Functional Bugs : Bugs found when Testing the Functionality of the AUT.
Technical bugs: Related to Communication which AUT makes.Like H/W,DB ! where these could not be connected properly.


Q - Give proper Seq. to following testing Types Regression, Retesting, Funtional, Sanity and Performance Testing.?
A - The proper sequence in which these types of testing are performed is - Sanity, Functional, Regression, Retesting, Performance.


Q - How u test MS- Vista without any requirement Doc.?
Know what change is being made from the older verison of Windows to the newer version with the help of User Release notes thats released with Windows Vista. Based on that, formulate the test cases and execute the same.


Q - What is verification? validation?

Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings. Validation typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation.


Q - How can new Software QA processes be introduced in an existing organization?

A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or property) projects, serious management buy-in is required and a formalized QA process is necessary.

Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand.

For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers.

The most value for effort will often be in (a) requirements management processes, with a goal of clear, complete, testable requirement specifications embodied in requirements or design documentation, or in 'agile'-type environments extensive continuous coordination with end-users, (b) design inspections and code inspections, and (c) post-mortems/retrospectives.


Q - Why is it often hard for management to get serious about quality assurance?

Solving problems is a high-visibility process; preventing problems is low-visibility. This is illustrated by an old parable: In ancient China there was a family of healers, one of whom was known throughout the land and employed as a physician to a great lord.


Q - What's an 'inspection'?

An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes.