Black Box Testing

BLACK BOX TESTING is  as defined as a testing technique in which functionality of Application  is tested without looking at the internal code and details of the software. This type of testing is based entirely on software requirements and specifications.

In BlackBox Testing we just focus on inputs and output of the software system without bothering about internal knowledge of the software.


This can be both Functional or Non-Functional


FUNCTIONAL TESTING:

In functional testing actions or functions of the system are being tested by providing the input and comparing the actual output with the expected output.

Few major types of Functional Testing are:

  • Smoke Testing
  • Sanity Testing
  • Integration Testing
  • System Testing
  • Regression Testing
  • User Acceptance Testing

NON- FUNCTIONAL TESTING:

There are several non-functional aspects as well that are required to be tested to improve the quality and performance of the application.

Few major types of Non-Functional Testing include:

  • Usability Testing
  • Load Testing
  • Performance Testing
  • Compatibility Testing
  • Stress Testing
  • Scalability Testing

How to do BlackBox Testing

  • Initially, the requirements and specifications of the system are examined.
  • Tester chooses valid inputs (positive test scenario) to check if softwhere or application processes them correctly. Also, some invalid inputs (negative test scenario) are chosen to verify that the application or Software  is able to detect them.
  • Tester make a note of expected outputs for all those inputs.
  • Software tester constructs test cases with the selected inputs.
  • The test cases are executed.
  • Software tester compares the actual outputs with the expected outputs.
  • Defects/ Bug if any are reported  and fixed and finally re-tested.

Tools used for Black Box Testing:

Tools used for Black box testing largely depends on the type of black box testing you are doing.

Black Box Testing Techniques-

  • Equivalence Partitioning
  • Boundary Value Analysis
  • Decision Table Testing
  • State Transition Testing
  • Error Guessing
  • Graph-Based Testing Methods
  • Comparison Testing

Advantages and Disadvantages

Advantages

  • The tester need not have a technical background. It is important to test by being in the user's shoes and think from the user’s point of view.
  • Testing can be started once the development of the project/application is done. Both the testers and developers work independently without interfering in each other’s space.
  • It is more effective for large and complex applications.
  • Defects and inconsistencies can be identified at the early stage of testing.

Disadvantages

  • Without any technical or programming knowledge, there are chances of ignoring possible conditions of the scenario to be tested.
  • In a stipulated time there are possibilities of testing less and skipping all possible inputs and their output testing.
  • A Complete Test Coverage is not possible for large and complex projects.



Comments

Post a Comment

Popular posts from this blog

SOFTWARE DEVELOPMENT LIFE CYCLE MODELS (SDLC MODEL)

Image
A software life cycle model is a descriptive representation of the software development cycle. SDLC models might have a different approach but the basic phases and activity remain the same for all the models. 1) Waterfall Model 2) V-Shaped Model 3) Prototype Model 4) Spiral Model 5) Iterative Incremental Model  6) Big Bang Model 7) Agile Model Waterfall Model The  Waterfall Model  was the first Process Model to be introduced. It is very simple to understand and use it. In a  Waterfall  model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.  The waterfall  model is the earliest  SDLC   approach that was used for software development. n “ The Waterfall ” approach, the whole process of  software development  is divided into separate phases. The outcome of one phase acts as the input for the next phase sequentially. This means that any phase in the development process begins only if the previous phase is complete. The waterfall model
Read more

DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE

Image
DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE  DEFECT: If  difference exist  between actual result and expected result  and that difference is found by developer and  corrected by himself in the development phase then it’s called a defect.   Example if developer  has developed  a code  and while performing (Unit Testing) developed  found that the code is not functioning  as per requirement  then in tat case the issue occurred  is known as DEFECT. BUG: If testers find any mismatch in the application/system in testing phase then they call it as Bug. Example if the developer has done the development  and performed Unit testing of a login form then the module is sent to Tester for performing testing. In this phase if tester found that the client requirement is not matching with the  result of application then tester report it as Bug.  NOTE:  there is a contradiction in the usage of Bug and Defect. People widely say the bug is an informal name for the defect. ERROR If we can’t compile
Read more

Software Testing Life Cycle (STLC)?

Image
STLC(SOFTWARE TESTING LIFE CYCLE) It is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle. PHASES OF STLC : Requirement Analysis Test Planning Test case development Test Environment setup Test Execution Test Cycle closure What is Entry and Exit Criteria? Entry Criteria:  Entry Criteria gives the prerequisite items that must be completed before testing can begin. Exit Criteria:  Exit Criteria defines the items that must be completed before testing can be concluded. Requirement Analysis During this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may in
Read more