welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...

image
Blog

‘Black Box Testing’ method

By Himanshu on 2/3/2014

Earlier I had written about Software Testing Life Cycle to improve the quality of the product and also automated testing tool, today I will share my thoughts related ‘Testing Methodology’ which I experienced while I performed the tests. There are primarily two testing methodology to test software today, I will discuss about the ‘Black Box Testing’ method. 

Text Box: #666464 Box TestingBasically in this method software/application is analysed/tested by a tester without being aware of its implementation/design/structure while the test can be functional/non-functional, usually functional is preferred.

                                                                     

 

 

Cube: Executable Program
Right Arrow: Output
Right Arrow: Input

 

 



Text Box: Tester unaware of implementation/design/structure while the test                                                     

 


This process is termed as ‘black Box’ because, in the judgement of the Quality assurance tester, the internal working is hidden inside which tester doesn't know.

The method of attempts to discover errors in sets are following:

  • Behavior/performance errors

  • Interface errors

  • Incorrect or missing functions

  • Initialization/termination errors

  • Errors in data structures/external database access 

We can take an example of a tester, without any information of the design/structure of a website, begins to test the website on browser; providing random different types of inputs and many clicks, keystrokes and validating the outputs compared to the expected outcome. 

Following are some techniques are used for designing black box tests.

Equivalence partitioning- It involves dividing input values into valid & invalid partitions and go for the representative values from each partition as test data.

Boundary Value Analysis- It involves determination of boundaries for input values & selecting values that are at the boundaries and just inside or outside of the boundaries as test data.

Cause Effect Graphing- It involves identifying the cases (input conditions) and effects (output conditions), producing a Cause-Effect Graph, and generating test cases subsequently.  

Testing Tools
‘Black Box Testing’ method
Black Box Testing
METHODOLOGIES of Software Testing
Author
Blog Calendar
Blog Calendar List
2019 Nov  7  1
2019 Jan  22  3
2018 Dec  27  4
2018 Nov  61  3
2018 Oct  12  3
2018 Sep  92  11
2018 Aug  4  2
2018 Jun  11  1
2018 Jan  49  2
2017 Sep  506  5
2017 Aug  16  1
2017 Jul  15  2
2017 Jun  43  2
2017 May  17  1
2017 Apr  31  2
2017 Mar  110  4
2017 Feb  375  4
2016 Dec  174  3
2016 Nov  323  8
2016 Oct  224  10
2016 Sep  354  6
2016 Aug  38  1
2016 Jun  1709  6
2016 May  103  3
2016 Jan  70  2
2015 Dec  385  6
2015 Nov  3  1
2015 Oct  12  1
2015 Sep  1274  6
2015 Aug  12  1
2015 Jul  117  2
2015 Jun  8  1
2015 May  20  1
2015 Apr  21  2
2015 Mar  71  3
2015 Jan  5130  4
2014 Dec  15  1
2014 Nov  2190  4
2014 Oct  75  2
2014 Sep  98  2
2014 Aug  3604  1
2014 Jul  42  2
2014 Apr  2439  12
2014 Mar  273  19
2014 Feb  226  8
2014 Jan  1510  16
2013 Dec  21  2
2013 Nov  625  2
2013 Oct  246  3
2013 Sep  10  1
2013 Aug  30  3
2013 Jul  203  1
2013 Apr  46  6
2013 Mar  1762  10
2013 Feb  292  4
2013 Jan  259  2
2012 Nov  29  2
2012 Oct  420  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote