Difference between defect,error,bug,failure and fault Error: A discrepancy between a computed, observed, or measured value or condition and the

true, specified, or theoretically correct value or condition. See: anomaly, bug,defect,exception,andfault Failure: The inability of a system or component to perform its required functions within specified performance requirements. See: bug, crash, exception,fault.

Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner. See: anomaly, defect, error, exception,fault.

Fault: An incorrect step, process, or data definition in a computer program which causes the program to perform in an unintended or unanticipated manner. See: bug, defect,error,exception. Defect: Mismatch between the requirements.

Difference between Smoke testing or Sanity testing SanityTesting: Sanity testing is used to test in intial check up is made on the build after recieving from developer. Sanity Testing: When a major bug is filed in a build,developers will fix that particular bug alone and releases a new build ,testing the new build to check the particular issue is fixed and fixture has not caused any impact on other functionality,isknownas"SanityTesting" SmokeTesting: In this we test that application is able for the further testing or not. We just check the We during ii)Installed capability can of check installation application properly the application following of connected with things the the database for testing. in this: application). and network.

i)Build is properly installed on the system( because sometimes application crash

iii)All the module are display and working fine.

Difference between varification and validation verification:

Verification ensures the product is designed to deliver all functionality to the customer; it 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: Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed Difference between Static or Dynamic testing? StaticTesting: The Verification activities fall into the category of Static Testing. During static testing, you have a checklist to check whether the work you are doing is going as per the set standards of the organization. These standards can be for Coding, Integrating and Deployment. Review's, Inspection's and Walkthrough's are static testing methodologies.

DynamicTesting: Dynamic Testing involves working with the software, giving input values and checking if the output is as expected. These are the Validation activities. Unit Tests, Integration Tests, System Tests and Acceptance Tests are few of the Dynamic Testing methodologies. STLC(Software Testing Life Cycle) Order of STLC: Test Strategy what is the purpose of software testing's - Bug removal, System Test Plan what is the purpose of software testing's - Bug removal, System Test Scenario Test Case

Test Strategy:

Test Strategy is a Document, developed by the Project manager, 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", "Who to Test". Test Scenario: A name given to Test Cases is called Test Scenario. These Test Scenario was deal by the Test Enggineer. Test Cases: It is also document and it specifies a Testable condition to validate a functionality. These Test Cases are deal by the Test Enggneer Severity and Priority for bugs Give me example for BUG that has HIGH SERVERITY and LOW PRIORITY and SAME BUG in other case should be LOW SEVERITY and HIGH PRIORITY. Note : It should be SAME BUG NOT TWO DIFFERENT BUGS

Low severity: Application crasher from only one customer in 1000 customer that to for wrong usecase. High severity: Where as application crashes ,but prority is very less to fix the bug and will effectonlyonecustoer High prority & Low severity: Suppose you are having a bug that there is a spelling in the name of the project/product.Here the severity is less as it does not effect any thing,but the prority it should fix why bcoz this bug is very high prority,if any one catch it the image of the project or prodct will effect and get bad impression.so this is high prority.

Before answering this question i would like to say some thing abt my project, mine is a project, it contains both US and UK clients... but both are using same files... Desc about some functionality: A user can do volunteering to any of the charity with some hours, say for example he has volunteered 40 hours for a charity then he can elible to apply for some grant from his company, again this grant will goes to charity. HIGH SERVERITY and LOW PRIORITY Issue: Now the issue is out of all users applications works perfectly, but not worked only for one user who done his volunteering in last year other than this year, in this case we can consider this as High sev and low priority if the release time is over for testing team perspective. LOW SEVERITY and HIGH PRIORITY. The same issue will considered as Low severity and high priority in client perspective as he has so many clients.

What are latent bugs?

What is build interval period?

In some companies specially in J2EE domain, builds are delivered from development team to the testing team to start the system testing. For example a new product XXX is being released to the testing team so the dev team will deliver a build to the Testing team. Now Testing team will do the testing and then will release the product to the client. Now there is a new version of the product coming up with the name XXX.1 and is being released to the testing team, so this will be the second build and the time between these 2 builds will be called as build interval. What is the Difference between End to End Testing & System Testing. System Testing Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.End-To-End Testing Similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use

system testing: is process of attempting to demonstrate the program. Is done by testing group before the product is made available to the customer. it tests whether all applications are availabe functionalities modules are there for application for testing after intergation and unit testing.