Tuesday, April 22, 2008

Software Testing Interview Questions 9

Q. 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?
A: — Test case would have detail steps of what the application is made-up to do. SO

1) Functionality of application is acknowledged.

2) In addition you can refer to Backend, I mean glance into the Database. To gain more information of the application

Q. How to execute test case?
A: — There are two ways to execute test case:
1. Manual Runner Tool for manual execution and updating of test status.
2. Automated test case execution by specifying Host name and other automation pertaining details.

33. Difference between re testing and regression testing?

A: — Retesting: –

Re-execution of test cases on same application put up with different input values is retesting.

Regression Testing:

Re-execution of test cases on updated form of build is called regression testing…

Q. What is the difference between bug log and defect tracking?
A; — Bug log is a document which keep the information of the bug where as bug tracking is the process.

Q. Who will change the Bug Status as Differed?
A: — Bug will be in open position while developer is working on it Fixed after developer completes his work if it is not fixed correctly the tester puts it in reopen After fixing the bug properly it is in closed state.

Q. What is smoke testing and user interface testing ?

A: — ST:
Smoke testing is non-exhaustive software testing, as pertaining that the most critical functions of a program work, but not worry with higher details. The term comes to software testing from a similarly basic type of hardware testing.

UIT:
I did a bit or R n D on this…. some says it’s nothing but Usability testing. Testing to find out the simplicity with which a user can learn to work, input, and interpret outputs of a system or component.

Smoke testing is nothing but to make sure whether essential functionality of the build is stable or not?
I.e. if it possesses 70% of the functionality we say build is stable.
User interface testing: We verify all the fields whether they are existing or not as per the format we check spelling graphic font sizes the whole thing in the window present or not|

Q. What is bug, defect, issue and error?

A: — Bug: — Bug is recognized by the tester.
Defect:– Whenever the project is received for the analysis phase ,may be some requirement neglected to get or know most of the time Defect itself come with the project (when it comes).
Issue: — Client site error most of the time.
Error: — When something is happened wrong in the project from the development side i.e. called as the error, most of the time this knows by the developer.

Bug: a fault or defect in a system or machine

Defect: an imperfection in a device or machine;

Issue: An issue is a major problem that will slow down the development of the project and cannot be determined by the project manager and project team without outside help

Error:
Error is the deviation of a measurement, observation, or calculation from the truth

Q. What is the diff b/w functional testing and integration testing?
A: — functional testing is testing the complete functionality of the system or the application whether it is meeting the functional terms

Integration testing means testing the functionality of integrated module when two different modules are integrated for this we use top-down approach and bottom up approach

Q. What sort of testing you make in organization while you do System Testing, give clearly?

A: — Functional testing
User interface testing
Usability testing
Compatibility testing
Model based testing
Error exit testing
User help testing
Security testing
Capacity testing
Performance testing
Sanity testing
Regression testing
Reliability testing
Recovery testing
Installation testing
Maintenance testing
Accessibility testing, including compliance with:
Americans with Disabilities Act of 1990
Section 508 Amendment to the Rehabilitation Act of 1973
Web Accessibility Initiative (WAI) of the World Wide Web
Consortium (W3C)

Q. What is the major use of prepare Traceability matrix and clarify the real time usage?

A: — A traceability matrix is formed by associating necessities with the work products that satisfy them. Tests are linked with the requirements on which they are based and the product tested to assemble the requirement.

A traceability matrix is a statement from the requirements database or repository.

Q. How can you do the following 1) Usability testing 2) scalability Testing

A:–
UT:
Testing the simplicity with which users can learn and use a product.

ST:
It’s a Web Testing allows web site ability development.

PT:
Testing to find out whether the system/software meets the specified portability requirements.

Q. What does you mean by Positive and Negative testing & what is the difference between them. Can anyone explain with an example?

A: — Positive Testing: Testing the application functionality with suitable inputs and confirming that output is right


Negative testing: Testing the application functionality with unacceptable inputs and verifying the output.

Difference is nothing but how the application perform when we enter some unacceptable inputs suppose if it accepts invalid input the application Functionality is wrong

Positive test: testing meant to show that s/w work i.e. with applicable inputs. This is also called as “test to pass’
Negative testing: testing aimed at showing s/w doesn’t work. Which is also know as ‘test to fail” BVA is the best example of -ve testing.

Q. What is change request, how u use it?

A: — Change Request is an attribute or part of Defect Life Cycle.

Now when you as a tester find a defect and report to your DL…he in turn informs the Development Team.
The DT says it’s not a defect it’s an extra implementation or says not part of requirement. Its newscast has to pay.

Here the status in your defect report would be Change Request

I think change request controlled by change request control board (CCB). If any changes required by client after we start the project, it has to come thru that CCB and they have to approve it. CCB got full rights to accept or reject based on the project schedule and cost.

Q. What is risk analysis, what type of risk analysis u did in u r project?

A: — Risk Analysis:
A systematic use of accessible information to decide how frequently specified events and unspecified events may happen and the magnitude of their likely consequences4

No comments:

My Ad

.