|
This course presents a blend of both foundation and intermediate level testing concepts. It provides the attendee with an excellent introduction to software testing. It discusses the basics including definitions and methodologies, techniques for testing including black, gray and white box, explores the various definitions of a “unit” and how to test various units. It also provides several excellent approaches for testing at a unit level. Finally, it introduces several examples of automated testing tools and the use of good test metrics to improve both the effectiveness and efficiency of unit testing.
Additionally, this program provides an excellent forum for companies to improve organizational communication and coordination. This program will help associates who are involved in development, quality assurance, quality control and all phases of testing, etc. by understanding and using the same testing vernacular, terms and concepts.
This is a one-day course.
Need to train multiple people on this topic? Try Private in-house training.
For more information contact Tim Pelland or Bill Marinara at info@qaicampus.org or 1-866-724-6013 |
|
Section/Topics
- Test Basics
- Test Techniques
- Unit Testing Defined
- An approach for Unit Testing
- Test Tools
- Test Metrics
Section 1. Test Basics
- Testing Myths / Testing Truths
- What is a process:
- Process components
- Sources of variability
- What is testing?
- What is a Unit?
- One program module
- One function/feature
- In Object-Oriented:
- A Class or
- The functionality implemented by a method
- A window or elements of a window
- A web page
- A Java servlet
- An Active Server Page (ASP)
- Dynamic Link Library (DLL)
- Servers:
- Applets
- Common Gateway Interfaces (CGI)
- What is a Unit Test?
- Why do we test units?
- What are the attributes of a good test?
- “V” Model
- Defect management and reporting
- Risk based approach to testing
Section 2. Test Techniques
- Black Box testing
- Requirements based
- Equivalence partitioning
- Boundary value analysis
- White Box testing:
- Basic dynamic alternatives:
- Code coverage
- Path coverage
- Decision coverage
- Condition coverage
- Error coverage
- Data coverage
- Unit Interfaces
- Advanced considerations:
- Usability
- Performance
- Stress/Load
- Forced Error Testing
- Gray Box testing
- Testing aids:
- State diagrams
- Activity diagrams
- Traceability
Section 3. Unit Testing Defined
- Test artifacts:
- Unit test plan
- Unit test scripts
- Unit test data
- Change control
- Reuse
- Test Roles/responsibilities
- Unit test objectives
- Collaboration with the QA staff
- Don’t overlook regression testing as an alternative
Section 4. An Approach for Unit Testing
- Step 1. Define unit test objectives
- Step 2. Select a test technique
- Step 3. Perform a requirements/design walkthrough
- Step 4. Perform data analysis
- Step 5. Identify test environment needs
- Step 6. Develop test scripts
- Step 7. Populate test files
- Step 8. Develop drivers and/or stubs
- Step 9. Execute test
- Step 10. Review results
- Step 11. Identify defects
- Step 12. Report Results
Section 5. Test Tools
- Automated and manual support
- Test tool examples
Section 6. Test Metrics
- Align metrics to objectives
- Test metrics examples
|
|
Quality Assurance Analysts, Testers, Developers, Software Project leaders / Managers, IT managers, Business Analysts |
|
|
Date |
City, Province/State |
|
April 16, 2008 |
Indianapolis, IN |
Registration CLOSED |
Sept. 18, 2008 |
Los Angeles, CA |
To Be Announced |
| April 22, 2009 |
Indianapolis, IN |
To Be Announced |
|
|
|
$495 per attendee (QAI Members receive a 10% Discount) |
Start Time ~ 9:00 am
End Time ~ 4:30 pm |
| The price includes the course material, lunch & breaks of the given day, and a certificate of completion. Hotel and travel arrangements are the responsibility of the attendee. |
|
- All cancellations must be made in writing - either by mail, e-mail, or fax.
- All payments must be received by QAI prior to the start of the conference/seminar.
- If cancelled 5 calendar days, or later, prior to the start date or for no-shows - NO REFUND
- If cancelled 6-30 calendar days prior to the start date - 50 % of the conference/seminar fee will be non-refundable.
- If cancelled prior to 30 calendar days to the start date - A full refund will be issued.
- You are welcome to substitute if you cannot attend, but please notify in advance.
- You may reschedule with at least four weeks notice prior to the conference/seminar for which you are currently registered.
- Please send all cancellations and substitutions to register@qaiworldwide.org, or fax to 407-363-1112, Attn: Registrar
|
|
|