Black Box Testing Training
Black Box Testing Training Course Introduction:
Black Box Testing Training is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. Black Box Testing Training method of test can be applied to virtually every level of software testing: unit, integration, system and acceptance. A black box software tester selects a set of valid and invalid input and code execution conditions and checks for valid output responses.
Global Online Trainings offers Black Box Testing Training online classes with flexi hour advantage and with most reasonable fee. Black Box Testing Training tutorial, made here with best industry updates. To know more detail about this module call /mail the help-desk.
Black Box Testing Training Course Content
Introducing Test Types
- Software Development Stages Overview
- Planning Stages
- Testing During the Planning Stages
- Design Stages
- Testing During Design Stages
- Glass Box Code Testing is Part of the Coding Stage
- Regression Testing
- Behavioral Testing/Black Box Testing
Identifying Equivalence Classes and Boundary Values
- Equivalence Partitioning
- Analysis of Boundary Value
- Beyond Functional Classes and Boundaries
- Equivalence Classes & Boundary Values Exercise
Building Decision Tables for Testing
- Use Cases and Scenario Tests
- Nouns and Verbs, Adjectives & Adverbs
- Live Data and Customer Tests
- Decision Tables
- Decision Table Exercise
Working with State Transition Diagrams
- Describing Systems with the States Using State Transition Diagrams
- State Tables
- State Transition Diagram Example
- State Transition Diagram Exercise
Implementing Domain Testing
- A Simple Domain Testing Example
- Domain Test Values
- Domain Testing Example
- When Domain Rules Change
- Domain Analysis Summary
- Example of Complex Domain Testing
- A General Rule for Complex Domains
- Domain Testing Exercise
Applying Orthogonal Arrays & All Pairs for Testing
- Orthogonal Arrays & All-Pairs Tables
- Two Orthogonal Arrays
- Selecting an Orthogonal Array
- Applying Orthogonal Arrays
- All-Pairs Tables
- Configuration Testing
- Orthogonal Arrays Exercise
Performing Reactive Testing
- General Facts about the Reactive Tests
- Error Guessing, Attacks, and Bug Taxonomies
- Bug Hunting
- Exploratory Tests and Checklists
- Other Sources of Inspiration for Reactive Testing
- Advantages and Disadvantages
- Exploratory Testing Exercise
Black Box Testing Overview:
- Black Box Testing is to just test the application without bothering about the programming language developer is using, how converting the input into output etc.
- Here we just test the application as a user by giving different sets of test data to the application to check the performance of the application based on the output.
- After that we will check whether the output we received is up to our expectations.
- If not then there might be some Bug in the application, which is reported back to the developer in the form of an Excel sheet as a testing error.
- The bug you need to represent simply like the actual output is not equal to the expected output than we can report it as the bug to the developer.
- Black Box Testing is also named as:
- Closed Box Testing
- Functionality Testing
- Behavioural Testing
Black Box Testing – Closed Box Testing:
- Black Box Testing is also known as the Closed Box Testing , simply the box is closed or the application is closed that means we are not going into the application, we are just testing it as a user.
- For example, we are testing for the Gmail login that it will ask to provide username and password.
- Here we perform the testing in two scenarios; first we will give the valid username and password and will click on sign – in.
- If we sign in properly than we can assure that the first scenario is working properly.
- In the second case we will provide with the invalid username and password, and then it should show us the error like enter valid username or password.
- If it gets login – in without showing the error, we can send it as Bug to the developer.
- Here the Box is closed, we are just testing the application without knowing its features.
Black Box Testing – Functionality Testing:
- Here we will test the functionality of the application in the same way as we did for the closed box testing.
- Likewise we discussed in the closed box testing for gmail login.
- If we give valid user name and password than it should login.
- If we give the invalid username and password than it should not be login
Black Box Testing – Behavioural Testing:
- Here this is to check the behaviour of the application by providing the different sets of input data.
- Different input are tested onto the application to calculate the proper working of the application.
Types of Black Box Testing:
Black Box is broadly divided into four types:
- Usability Testing
- Functionality Testing
- Security testing
- Performance testing
Black Box Testing Training On Usability Testing:
- It’s a type of testing where it focuses and more concern about the user interface.
- To test that how much attractive the user interface is, how much good and how mush friendly my user interface is.?
- Simply we can say to check the look of the application in the user point of view.
- As the main purpose of the creating the application or website is to generate traffic to the application.
- So that more people visit our application or website, if the look and feel of the application is good.
- As every organisation want people to visit their application not only once but they want the people to revisit again and again.
- This is possible if and only if we have the user friendly application because people visiting our application should not find any complications.
- The visitor should get the prompt result or information in our application which is looking for without any complications.
Types of Usability Testing:
User Interface testing:
Application should have user friendly interface. Customers should be able to access application easily. Again in focus on three main factors like easy to use, look & feel and quick interface.
Easy To Use: Application should be easy to use. To verify, that the application is easy to use or not. Microsoft has given 6 rules for this:
- Control should be well defined. The purpose of every control should be clear.
- Control should not be truncated or wrapped. Control should be properly placed, should not be overlapped.
- Control should provide complete description.
- Initcap (First letter of every word should be capital)
- Spell-Checking (No spelling mistakes)
- System menu (short cut menu/ Right Click menu)
Look And Feel: Application should maintain consistency in terms of fonts, colours.
Quick Interface: Application should provide quick navigation. Application must have most frequently pages appearing as link at top. Whatever client looking for, should be able to get that information quickly and easily
Manual support testing:
Application should have properly documented manual or help document. All features should be clearly mentioned in manual.
Black Box Testing Training on Functionality Testing:
- Executing the application for verifying its functionality. For Example : To check the login functionality of gmail.com, Enter Valid Credentials and then checking if able to login or not.
- And entering Invalid Credential and then checking what happens and checking if its displaying user friendly error message on screen.
Types of Functionality Testing:
Functional Testing: It is also known as positive testing. Entering valid username and valid password and checking if able to login or not.
Error Handling: It is also known as negative testing. Entering invalid credentials and checking if able to login or not and checking for user friendly error message on screen.
Compatibility Testing: It is also known as Software Compatibility. Application is verified for compatibility with 3 things:
a) Browser Compatibility: Application should work perfectly client’s browsers
b) Database Compatibility: Application should be compatible with client’s database.
c) Operating System Compatibility:Application should be compatible with client’s Operating System.
Configuration Testing: It is also known as Hardware Compatibility. Application should work perfectly with customer expected platform.
Installation Testing: Application should be easy to install. If some setting to be made prior to installation, those should be mentioned in installation manual.
Intersystem Testing: Application should be able to work with other systems.
Input Domain Testing: Verifying the application by passing multiple sets of data.
Black Box Testing Training on Security Testing:
Application should be secure. Private or sensitive information should not be leaked out. Application should maintain trust of customers by giving them sense that their information is in safe hands.
Black Box Testing Training on Performance Testing :
Verifying the performance of the application under customer expected. Application should not crash when undergoes customer expected load.
Types of Performance Testing:
Load Testing : Checking the performance under customer expected load.
Stress Testing : Checking the performance above customer expected load by continuously increasing stress.
Black Box Testing Training outline:
- Program Name: Black Box Testing Training course
- Course Duration: 35 Hours
- Mode: Online virtual classes and corporate
- Timings: According to one’s feasibility
- System Access : will be provided
- Batch Type: Regular , weekends and fast track
- Trainees will get the soft copy material.
- Sessions will be conduct through WEBEX, GOTOMEETING OR SKYPE.
- Basic Requirements: Good Internet Speed, Headset