Explain Seven Testing Principles

Being a Software Tester, we have to aware about Testing principles. Let's explain Seven testing principles below here:-

1. Testing shows presence of defects:- Testing never proves that there are no defects in the application. It only can show that defects are present in the application. Testing mitigates the probability of undiscovered defects existing in an application or in the software. Although, even if no defects are found in the software, it's not a that software is 100% correct.

2. Exhaustive testing is impossible:- Testing everything thoroughly (with all combinations of inputs & preconditions) isn't possible or feasible except trivial cases. We test an application on the bases of risks and priorities instead of exhaustive testing.

3. Early Testing:- Software testing activities should start at a very early stage of software development life cycle (SDLC) and should be focused on defined objectives.

4. Defect clustering:- A small numbers of units contain bunch of defects that are discovered during pre-release testing. or it shows the most operational failures.

5. Pesticide paradox:- If the same set of tests are repeated over and over again, ultimately the same set of test cases will no longer detect any new bugs. Therefore, to overcome this pesticide paradox, the test cases need to be regularly reviewed and revised.

6. Testing is context dependent:- Testing is performed differently in different contexts. For example:- critical or safety application is testing differently from an e-commerce site.

7. Absence-of-errors fallacy:- Detecting and fixing bugs or defects doesn't help if the system built doesn't fulfill the user's needs and expectations.

Thanks for reading my blog. Please leave comment below if you like this post.

Happy Testing..!!

Read More

Explain Build Verification Testing (BVT)?

Build Verification Testing (BVT) :- A build verification (BVT) test is a set of tests run on each new build of a product or software to verify that the build is testable, before sending it to the testing team. It is generally a short set of tests which exercise the mainstream functionality of the application. Any build that fails the build verification test is rejected, and testing continues on the previous build of the product, provided there has been at least one build that has passed the verification test. Build verification tests are highly important because they let developers know if there is any serious bug or problem with the build right away.

Continue reading...

Hi Readers, if you find it interesting, express yourself by commenting here..!!!

Read More

What is Black Box Testing? Advantages and Disadvantages of BBT.

Black Box Testing:- Black box testing is an approach where a tester test an application or a software without knowing the internal working of the Application Under Test (AUT). Black box testing is also referred to as functional testing, behavioral testing or input/output driven testing technique.

For example:- when this approach (black box) are applied on an application or a software, the tester only knows the inputs and what the expected outcomes should be, without knowing how the program arrives at those outcomes. For testers, it is like a black box, inside which one cannot see. Which is why we call it Black box testing.

Definition of ISTQB:-

"Testing, either functional or non-functional, without reference to the internal structure of the component or system."

Advantages of Black Box Testing:- 

• Tester can be non-technical.
• Tests are done from a user's point of view that will help in revealing discrepancies in the specifications.
• Black box tests can be re-used.
• Expose ambiguities and complexities in an application.
• Test cases can be designed as soon as the specification are complete.

Disadvantages of Black Box Testing:-

• Only a small number of test cases can be executed, and many program paths will be left untested.
• Reason for the failure of product cannot be determined.
• Quality of coding and adherence to coding standards will be unknown.
• Test cases cannot be designed or prepared without having clear specifications.

We can apply the following types of BBT to test an application:-

1. Build Verfication Testing (BVT)
2. Smoke Testing
3. Sanity Testing
4. Usability Testing
5. Functional Testing
6. Configuration Testing
7. Compatibility Testing
8. Retesting
9. User Interface Testing
10. Maintenance Testing
11. Regression Testing
12. Performance Testing

Read More

What is Retesting or Confirmation Testing?

Retesting or Confirmation Testing:- Retesting is done by the tester to ensure that the defects reported in the previous build has been fixed. In Retesting, tester re-run the failed test cases.

Lets consider a scenario where a build is found to have 15 defects, which are then assigned to the developers for fixing. Once all these defects or bugs are fixed by the developers, the build is retested to verify whether the defects or bugs have been fixed or not. which is why we call it retesting or confirmation testing.

(Defect/bugs verification is also a part of Re-testing).  


Latest Manual testing Interview Questions

Read More

Difference between Smoke Testing and Sanity Testing?

Difference between Smoke and Sanity Testing?

Smoke Testing :- Smoke Testing is a wide and shallow approach. It means we (Developer) test an application in a cursory way without going into too deep. Smoke Testing is basically performs to test the health of builds before handed over to the testing team for deep testing. It is done by developer. Some times it is also done by testers too. Smoke testing is scripted i.e. either we use test cases or automation script to test an application.

Why Smoke Testing performed?
Basically smoke testing is performed or conducted to make sure whether the most crucial functionalities of an application are working fine or not.

Sanity Testing :- Sanity Testing is deep and narrow approach. It means tester test a specific module or unit of an application thoroughly. It is also a subset of Regression testing. It is use to determine whether a small section or a module is working fine after a minor changes or not. Sanity testing is unscripted.

Why Sanity Testing performed?

Basically sanity testing is performed when developer wants to know the quick and fast status of the application after they have made changes in the code.

click here for Stubs and Drivers topic

Read More