White box testing and Black box testing

-

White Box Testing: 

White box testing is a testing technique, that examines the program structure and derives test data from the program code. The other names of glass box testing are clear box testing, open box testing, logic-driven testing or path driven testing or structural testing.
White Box Testing is the testing of a software solution's internal coding and infrastructure.
White box testing is also known as Clear Box testing, Open Box testing, Structural testing, Transparent Box testing, Code-Based testing, and Glass Box testing.

 Advantages of white-box testing :

  • Code optimization by finding a hidden error
  • White box tests cases can be easily automated.


 Disadvantages of white-box testing:  

  • White box testing can be quite complex and expensive. 
  • White box testing requires professional resources, with a detailed understanding of programming and implementation



Black box Testing:

Black-box testing is a method of software testing that examines the functionality of an application based on the specifications. It is also known as Specifications based testing. Independent Testing Team usually performs this type of testing during the software testing life cycle.
It is functional testing. The tester will get (.exe) file which is sent by the developer it is based line by the senior developer and we can’t change and edit in this tester will only do the execution. 

Advantages of black-box testing :
  • Unbiased tests because the designer and tester work independently.
  • The test is performed from a user’s point-of-view and not of the designer’s.
  • Efficient when used on large systems.
  • There is no need for the tester to have detailed functional knowledge of system
  • A tester can be non-technical.

Disadvantages of black-box testing:
  • Test cases are challenging to design without having clear functional specifications.
  • It is difficult to identify tricky inputs if the test cases are not developed based on specifications.
  • There is a high probability of repeating tests already performed by the programmer.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more