Please explain Answere my Question

[prashantchandan]

1> what is the difference between Quality control and Quality Assuarance.
2>What is the difference between Build verification testing And Sanity Testing.
3> what is the difference between Adhoc testing an Exploratory testiong

[vsachdeva]

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives.

QA activities ensure that the process is defined and appropriate. Methodology and standards development are examples of QA activities. A QA review would focus on the process elements of a project - e.g., are requirements being defined at the proper level of detail.

Quality Control: A set of activities designed to evaluate a developed work product.

QC activities focus on finding defects in specific deliverables - e.g., are the defined requirements the right requirements. Testing is one example of a QC activity, but there are others such as inspections

The difference is that QA is process oriented and QC is product oriented.
Quality Assurance makes sure you are doing the right things, the right way.
Quality Control makes sure the results of what you've done are what you expected.


BVT:Build Verification test is a set of tests run on every new build to verify that build is testable before it is released to test team for further testing. These test cases are core functionality test cases that ensure application is stable and can be tested thoroughly. Typically BVT process is automated. If BVT fails that build is again get assigned to developer for fix.
SANITY:A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep. A sanity test is usually unscripted. A Sanity test is used to determine a small section of the application is still working after a minor change. Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

Adhoc Testing: This testing is also called Gaurilla or Monkey Testing. This testing performs when very little amount of time to perform testing like one or two days. Ad hoc testing is concern with the Application Testing without following any test cases. For Ad hoc testing one should have strong knowledge about the Application.Ad hoc testing means doing something, which is not planned.


Exploratory Testing: An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.

[pwahi]

hi,pls find your answers below:


Exploratory testing is simultaneous learning, test design, and test execution .The essence of exploratory testing is that you learn while you test, and you design your tests based on what you are learning. The testing is dependent on the tester's skill of inventing test cases and finding defects. The more the tester knows about the product and different test methods, the better the testing will be. The main advantage of exploratory testing is that less preparation is needed, important bugs are found fast, and is more intellectually stimulating than scripted testing. Disadvantages are that the tests can't be reviewed in advance .When the requirement specification provided by the client is not enough to understand the application, exploratory testing is an effective approach .An experienced tester with domain knowledge of the product is the most suitable person to execute such type of testing.


Ad-Hoc Testing: It's a random testing of the application to find defects . It means testing an application without proper test plan. This type of testing is done without any specific procedure .Normally this type of testing is performed when there is no sufficient time to test the application .No formal test cases are prepared under this type of testing. Disadvantages of ad hoc testing is that there is no proof of how much testing is performed and also since nothing is documented we can even miss some important scenarios of application.


Software quality assurance consists of a means of monitoring the software engineering processes and methods used to ensure quality. It does this by means of audits of the quality management system under which the software system is created. These audits are backed by one or more standards, usually ISO 9000 or CMMI.SQA encompasses the entire software development process, which includes processes such as software design, coding, source code control, code reviews, change management, configuration management, and release management.It is a set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives. Software quality assurance is a control of processes. QA activities ensure that the process is defined and appropriate. Methodology and standards development are examples of QA activities. A QA review would focus on the process elements of a project - e.g., are requirements being defined at the proper level of detail. Quality Assurance makes sure you are doing the right things, the right way.


Quality Control: A set of activities designed to evaluate a developed work product.It includes reviewing requirements documents, and software testing. QC activities focus on finding defects in specific deliverables - e.g., are the defined requirements the right requirements. Testing is one example of a QC activity, but there are others such as inspections. QC is product oriented. Quality Control makes sure the results of what you've done are what you expected.

--i hope the above answers will clear your doubts-
parul