Test cases for Black box

For Black box testing, the test cases can be generated by using all or a combination of the below techniques.

Graph Based : Software testing begins by creating a graph of important objects and their relationships and then devising a series of tests that will cover the graph so that each objects and their relationships and then devising a series of tests that will cover the graph so that each object and relationship is exercised and error is uncovered.

Error Guesssing – Error Guessing comes with experience with the technology and the project. Error Guessing is the art of guessing where errors can be hidden. There are no specific tools and techniques for this, but you can write test cases depending on the situation. 

Boundary Value Analysis (BVA) is a test data selection technique (Functional Testing technique) where the extreme values are chosen. Boundary values include maximum, minimum, just inside/outside boundaries, typical values, and error values. The hope is that, if a system works correctly for these special values then it will work correctly for all values in between. 

Equivalence partitioning is a testing method that divides the input domain of a program into classes of data from which test cases can be derived.

Compasrision Testing – There are situations where independent versions of software be developed for critical applications, even when only a single version will be used in the delivered computer based system. It is these independent versions which form the basis of a black box testing technique called Comparison testing or back-to-back testing.

The Orthogonal Array Testing Strategy (OATS) is a systematic, statistical way of testing pair-wise interactions by deriving a suitable small set of test cases (from a large number of possibilities).

Test Activities during phases

Test activities vary with the model and also on the type of project. So here is a generic list of items that needs to be done. You can always do it at any point when enough data is available.

1. Requirement Phase :

• Invest in analysis at the begining of the project
• Start developing the test set at the requirement analysis phase
• The correctness, consistency and completeness of the requirements should be analysed.

2. Design Phase :

• Analysis of design to check its completeness and consistency
• Analysis of design to check whether it satisfies the requirements
• Generation of test data based on design
• Setting up of test bed

3. Programming/Coding Phase :

• Check code for consistency with design
• Perform system testing in an organized manner – Buddy testing, feature testing, integration testing, System testing etc
• Use available tools
• Apply stress to the program
• Test one at a time
• Measure test coovergae

4. Maintanence Phase :

• Retest/Regress

Automation workflow

How to Implement Test Automation Framework Methodology

1.Identification of the Scope of Testing: Company Oriented, Product Oriented, Project Oriented
2.Identification of the Needs of Testing: Identify Types of testing e.g. FT, Web Services etc. and application / modules to be tested.
3.Identification of the Requirements of Testing: Find out the Nature of Requirements, Identification of type of actions for each requirement & identification of High Priority Requirements
4.Evaluation of the Test Automation Tool: Preparation of Evaluation Checklist, Identification of the Candidate Tools Available, Sample Run, Rate & Select the Tool, Implementation & Training
5.Identification of the Actions to be automated: Actions, Validations & Requirements supported by the Tool
6.Design of the Test Automation Framework: Framework Guidelines, Validations, Actions Involved, Systems Involved, Tool Extensibility Support, Customs Messages & UML Documentation
7.Design of the Input Data Bank: Identification of Types of Input file, Categorization & Design of File Prototypes
8.Development of the Automation Framework: Development of Script based upon Framework Design, Driver Scripts, Worker Scripts, Record / Playback, Screen / Window / Transaction, Action / Keyword & Data Driven
9.Population of Input Data Bank: Different Types of Data Input, Population of Data from Different Data Sources, Manual Input of Data and Parent – Child Data Hierarchy
10.Configuration of the Schedulers: Identify Scheduler Requirements & Configure the Schedulers.

Performance counter – 4

Additional web counters  to monitor performance

ASP.NET -> Request Execution Time		Bear in mind that this is only the time it took to execute the mos recent request.
ASP.NET -> Requests Current		Total of waiting and executing requests.
ASP.NET -> Request Wait Time		If wait time is going up and CPU is low then opening up the threading options will probably help.  This could also indicate the need to additional hardware to hand the load.
ASP.NET -> Requests Queued
ASP.NET Apps -> Pipeline Instance Count	Make sure this is for the Web Service App	Only on thread at time can use a Pipelin instance.  So a sudden increase can indicate backend latency.
ASP.NET Apps -> Requests Executing	Make sure this is for the Web Service App
ASP.NET Apps -> Requests Total	Make sure this is for the Web Service App
ASP.NET Apps -> Requests/sec	Make sure this is for the Web Service App	How quickly are we handling requests?