Software Test Methodology Training Course Details:
At The Nussbaum Center for Entrepreneurship
1451 South Elm Eugene St., Greensboro, NC 27406
Instructor: Shaun Bradshaw
Duration: 1 day
Target Audience: Test Analysts & Test Leads
Costs: $595 per attendee
Services Testing Workshop
Join Zenergy for its upcoming services testing and automation workshop:
2019 Workshop Dates:
at The Nussbaum Center for Entrepreneurship
1451 South Elm Eugene St., Greensboro, NC 27406
QA Testers (Basic knowledge of testing; theory and practice)
Services Testing and Automation Workshop:
- Identify discrepancies in system documentation.
- Prioritize system functionality.
- Create effective and repeatable test cases.
- Execute test cases efficiently.
- Record test case results promptly and with sufficient detail.
- Report all defects, errors, and issues.
- Build a regression baseline for future releases using previously exercised test cases.
- Deliver quality documentation of the testing process.
- Work to ensure that the customer receives quality software.
- Tools and concepts that enhance participant’s ability to perform test analysis.
- How to create effective and repeatable test cases, regardless of the application platform or the testing tools used.
- How to efficiently execute test cases, including recording and reporting the results, and accumulate useful and meaningful test metrics.
- Proven, repeatable, and measurable process for developing and executing test cases.
- Techniques to verify system specifications are accurate and complete.
Introduction to QA & Testing Principles
This section introduces the student to the basic principles of QA and software testing, provides valuable statistics showing the importance of both, and discusses the expectations and responsibilities of a Test Analyst and Test Manager.
1) The Difference Between QA & Testing
a) What is QA?
b) What is Software Testing?
c) Why are They Important and How are They Different?
2) Defect Prevention & Defect Detection
a) The Rules and Results of Prevention
b) Comparison of Prevention and Detection
c) Prevention and Detection Activities
3) Test Analysts
a) Who are They?
b) What Do They Do?
Standard Software Test Methodology Overview
This section presents an overview of the basic concepts of standard testing methodologies including what Zenergy considers to be best-practice.
1) Standard software testing methodologies
c) Best practice methodology
2) Methodology Processes
a) Testing the Specification
b) Test Analysis
c) Test Case Writing
d) Verification of Test Readiness
e) Test Execution
f) Test Metrics
g) Post-Test Activities
Testing the Specification
In the beginning of a software project, team members typically have their own concept of the way the user’s requirements should be implemented. The key to having a quality application is getting everyone’s ideas to meld into one cohesive product. This is done using a specification document. This section teaches the student how to verify that a specification document is complete, accurate, and logical.
1) Understanding the User’s Requirements
a) Getting Involved at the Beginning
b) Reviewing and Analyzing Business Requirements
2) Reviewing a Specification Document
a) Independent Reviews
b) Team Walkthroughs
c) What to Do when No Specifications are Available
3) When Problems are Found
a) Reporting Specification Defects
b) Tracking Specification Defects
Test Analysis is arguably the most important step in best practice methodology. At a minimum, it establishes the types of testing to be performed and identifies the functions that need testing. This section describes how to use a specification document to determine the significant logical branches and functional areas of the application to be tested and generate a basis for creating test cases.
1) Why is Test Analysis Important?
2) Determining the Level of Testing Required
3) Performing the Appropriate Level of Analysis
4) Tools of the Trade
a) Requirements Matrix
b) Test Abstract
5) Creating a Test Case Design (TCD) Document
Writing Test Cases
Conducting a thorough system test relies on the completeness of the written test cases used in the test effort. Comprehensive test case documents define the purpose of each test, the procedures to be followed and the expected results. This section illustrates the proper method and format for writing effective and repeatable test cases.
1) Test Case Requirements
a) Six Questions Answered By the Test Case Document
b) Sections of the Test Case Document
2) What is a Test Case?
a) Test Case Document Example
b) Test Case Example
c) Run Log Example
3) Writing Effective Test Cases
a) Test Coverage
b) System Tests vs. Unit Tests
c) Specificity in Test Cases
d) Repeatable Test Cases
e) Positive & Negative Testing
f) Equivalence Class Partitioning
g) Pairwise Testing
4) Test Case Reviews & Walkthroughs
Verification of Test Readiness
Careful planning and preparation of the test environment is crucial to a successful and efficient test effort. Therefore, it is important to verify the validity and readiness of each component of the test environment prior to the execution of the test cases. This section discusses the verification activities that should take place prior to executing test cases.
1) Verification Tasks
2) Test Environment Checklist
b) Environment Software
3) Verification Sign-off
An efficient and orderly approach is important once test execution begins. This helps to maximize the benefits of the planning that took place earlier in the test effort. There are a number of key ideas and activities presented in this section that will permit the student to ensure that this phase, one that is often subjected to last minute changes in scope and duration, is completed on time and with the greatest impact on the final product.
1) Determining Test Priorities
a) Testing New Functionality
b) Testing Complex Functions
c) Regression Testing
2) Executing Test Cases
a) Follow the Rules of Execution
b) Adhere to the Change Management Process
c) Track the Results – The Run Log
d) Update the Test Cases
3) What if the Test Case Fails?
a) Investigating Failures
b) Reporting & Tracking Failures
Test Metrics – Tracking the Results
The word metric is defined as “a standard of measurement”. Metrics can be used to track and measure the efficiency, effectiveness, and the success and shortcomings of the various activities and components of projects. While it is important to recognize the value of gathering metrics data, it is the interpretation of that data which makes the metrics meaningful. This section describes the metrics tracked during a test effort. Furthermore, it explains how to interpret the metrics so they are meaningful to the project.
1) The Metrics Philosophy
a) Keep Them Simple
b) Make Them Meaningful
c) Track Them
2) Metrics to Track
a) Types of Metrics
i. Base Metrics
ii. Calculated / Management Metrics
b) How Metrics are Calculated
3) How Metrics are Used – Introduction to Test Management Metrics
This section defines the post-test activities that allow a test team to gauge the effectiveness of the test effort and provide a basis for accurate planning of future releases. Each test effort yields valuable lessons and data that can be applied to future test efforts and software development projects.
1) The Test Summary Report
a) Sections of the Report
b) Information in the Report
2) Closeout Activities
a) Prepare/Modify the Regression Baseline
b) Test Retrospective
c) Data Cleanup
d) Project Archives
Using What You Learned
A great deal of information is available on the various methodologies and processes that can be used to achieve an effective, efficient, and repeatable test effort. Unfortunately, the information is useless if it is not put into practice. Furthermore, not all processes will work in every situation. This final section discusses the steps necessary to begin implementing the processes taught throughout this course.
a) What are the Testing Needs of the Organization?
b) Which Processes should be Implemented?
c) Who should be involved?
d) How should the Processes be Implemented?
e) When should the Processes be Implemented?
a) Assign the Tasks
b) Manage the Plan
a) Implement the Processes
b) Track the Metrics
c) Modify if Necessary
4) Final Q & A
a) Using Testing/QA Tools
b) Common Problem Areas
i. Resource Deficiencies
ii. Budget Constraints
iii. Lack of Management Support
c) Other Questions.
Zenergy’s staff experts in Agile, DevOps, and quality are in high demand as industry consultants, practitioners, and speakers at the largest software conferences in the world.
From mobile test automation using leading tools to manual testing on mobile devices, Zenergy has the experience to ensure mobile sites and apps perform as expected.
Test automation works best when implemented with a solid strategy. Zenergy has the experience to ensure your automation scales and performs like you want.
Zenergy not only houses leading QA and testing experts, it also employs large teams of automation engineers and test specialists in its onshore facility.
From basic and advanced Selenium Automation courses to Test Methodology, Agile, and more, Zenergy can meet your training needs.