Black Box Testing Techniques

About this workshop
Black box testing is a strategy in which testing is based solely on the requirements and specifications. Unlike its complement, white box testing, black box testing requires no knowledge of the internal paths, structure, or implementation of the software under test. This two-day onsite mentor-led jumpstart provides a practical rather than theoretical discussion of the purpose and nature of black box testing techniques. This jumpstart workshop also emphasizes methodologies for the design of effective test cases based on black box testing techniques.

Duration
2 days

Upon completion
Participants will be able to:
· Describes the equivalence class testing technique, boundary value testing technique, decision table testing technique, pairwise testing technique, state-transition testing technique, domain analysis testing technique, and use case testing technique
· Describes the applicability of the equivalence class testing technique, boundary value testing technique, decision table testing technique, pairwise testing technique, state-transition testing technique, domain analysis testing technique, and use case testing technique.
· Describes the limitations of the equivalence class testing technique, boundary value testing technique, decision table testing technique, pairwise testing technique, state-transition testing technique, domain analysis testing technique, and use case testing technique.

Workshop Agenda

1: Black Box Testing Techniques
· Definition
· Applicability
· Disadvantages
· Advantages

2: Equivalence Class Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

3: Boundary Value Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

4: Decision Table Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

5: Pairwise Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

6: State-Transition Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

7: Domain Analysis Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

8: Use Case Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

White Box Testing Techniques

About this workshop
White box testing is a strategy in which testing is based on the internal paths, structure, and implementation of the software under test. Unlike its complement, black box testing, white box testing generally requires detailed programming skills. This one-day onsite mentor-led jumpstart provides a practical rather than theoretical discussion of the purpose and nature of white box testing techniques. This jumpstart workshop also emphasizes methodologies for the design of effective test cases based on white box testing techniques.

Duration
1 day

Upon completion
Participants will be able to:
· Describes the control flow testing technique and data flow testing technique.
· Describes the applicability of the control flow testing technique and data flow testing technique.
· Describes the limitations of the control flow testing technique and data flow testing technique.

Workshop Agenda

1: White Box Testing Techniques
· Definition
· Applicability
· Disadvantages
· Advantages

2: Control Flow Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

3: Data Flow Testing
· Technique
· Examples
· Applicability and Limitations
· Summary
· Practice

Black Box and White Box Testing with Visual Studio Team System Jumpstart

About this workshop
The software development processes provide a general framework for developing software. The “software development process” in and of itself is not a set of guidelines by which to develop software. Rather, it’s a set of terms in which you can describe and discuss many different development methodologies - Waterfall, CMMI, Scrum, and eXtreme are all different software development processes that vary greatly in their actual implementation but share common phases in one form or another. These are all under the larger umbrella of “Software Development Life Cycle (SDLC)”. Often, these different processes are formalized by different organizations, and sometimes government organizations. CMMI, for example, is managed by the Software Engineering Institute, or Rational Unified Process by IBM. Visual Studio Team System (VSTS) provides an ability to author tests, run tests, and, most importantly in the context of SDLC, publish and share the results with your team and the management of your team. This two-day onsite mentor-led jumpstart provides you with the knowledge and skills to implement black box and white box testing techniques with VSTS.

Duration
2 days

Prerequisites
- Experience with any structured programming languages or object-oriented programming languages
- Attended K365Labs Black Box Testing Workshop
- Attended K365Labs White Box Testing Workshop

Upon completion
Participants will be able to:
- Describe the testing tools and also the user interface for creating, authoring, executing, and managing tests including: Unit tests, Web tests, Load tests, Manual tests, Ordered tests, Generic tests, Third-party tests
-Describe the analysis tools and also the user interface for executing analysis including: Code analysis, Dynamic analysis
- Describe the integration points into Visual Studio Team System Team Foundation Server.

Workshop Agenda

1: Overview of Visual Studio Team System
· Test Types
· Test User Interfaces
· Analysis Tools
· Handson
. Question and Answer

2: Unit Testing with Visual Studio Team System
. Overview of Unit Testing
. Unit Testing in Visual Studio Team System
. Advanced Unit Testing in Visual Studio Team System
· Handson
. Question and Answer

3: Manual, Ordered, and Generic Test Types in Visual Studio Team System
. Manual Test Type
. Ordered Test Type
. Generic Test Type
· Handson
. Question and Answer

4: Load Testing in Visual Studio Team System
. Creating a Load Test
. Components of a Load Test
. SQL Tracing
. Using a Test Rig
. Results Store
. Best Practices
. Running a Load Test
. Investigating Results
. Reporting Results
· Handson
. Question and Answer

5: Code Analysis and Dynamic Analysis
. Code Analysis
. Dynamic Analysis
· Handson
. Question and Answer