Software Testing Training | QTP, QC, ISTQB, LoadRunner, CSTE, Mercury, Rational Certifications

Comprehensive Functional Testing with IBM Rational Robot
Course Code : CTROB 300 Source : CresTech Course Length : 2 days

This course is designed to familiarize testing professionals with the basics of Rational’s functional test automation tool, Rational Robot. Students will be provided with hands-on instruction, from simple record/playback techniques to advanced test scripting concepts. Rational TestManager will be used to organize and process test results to facilitate data analysis. The focus will be on applying Rational Robot to resolve common automated testing challenges and to build effective, versatile test scripts through best practices and savvy usage of SQABasic code. At the conclusion of this module, principles learned will be applied to a .NET-based sample application.
Further this course gives students a foundation in the SQABasic scripting language and automated testing techniques. Learn to create test scripts that are more robust, durable and easier to maintain. The course includes lecture, workbook exercises and labs.

The advanced module is designed to give students a foundation in the SQABasic scripting language and automated testing techniques. Learn to create test scripts that are more robust, durable and easier to maintain. This module includes lecture, workbook exercises and labs.

Intended Audience

New Rational Robot, TeamTest, TestStudio, or Enterprise users. The principles taught in this course apply to all environments that Robot supports. The course is designed primarily for Quality Assurance professionals who will be using the automation tools.
The audience might also include QA practitioners, managers, or team leaders who are responsible for interacting with testers or who need to ensure that tools are being implemented fully and appropriately.
Course Objectives
At the end of the course, you will be able to:

Describe the function and purpose of Rational Robot.
Navigate the Rational Robot interface.
Apply good scripting practices.
Record and play back automated scripts.
Use Verification Points in an appropriate context.
Modify scripts to extend test capability and reduce script maintenance.
Create data-driven tests
Prerequisites

You must have a solid understanding of:

Microsoft Windows operating systems
Microsoft Windows applications
Be familiar with the following:

Quality Assurance processes
Programming principles and techniques
Course Outline

Benefits of using Rational Robot to automate tests
Test script development process
Contents of a Rational Project and test datastore
Recording, debugging, and playing back techniques
Setting the record and playback options for Rational Robot
Developing and executing shell scripts
Inserting verification points and wait states to ensure test script reliability and validity
Regression testing using existing Rational Robot test scripts
Using the test log and verification point comparators to investigate and analyze test results
Using SQABasic to edit test scripts to extend their functionality and reduce maintenance
Creating custom verification points
Using datapools and data files
Testing a .NET application
Variables: declaration, datatypes, scope
Operators: mathematical, logical, string
Object Scripting - Terminology, meaning, common commands, types of properties, return values
Control Flow Structures: if¦then¦end if and select case statements; loops (for next while doloop)
Use of Dialog and Input Boxes
User-defined functions and sub procedures; header, source, library and template files
Dynamic Verification Points
Robot Debugger
String manipulation
Arrays: static and dynamic; single and multidimensional
Data handling techniques and routines
Files: creating, reading from, writing to
Database access through SQL calls
COM object creation

Web Testing

http://www.crestechsoftware.com

Comprehensive Business Process Testing 9.2
Course Code : CTMBPT 540 Source : CresTech Course Length : 2 days

This introductory course provides an in-depth examination of the role of the Automation Engineer in a Business Process Testing (BPT) environment. You will learn the process of creating BPT components and tests using both QuickTest Professional and QualityCenter. You will also study how to create and manage BPT application areas, object repositories, keywords, functions and scripted components. Best practices for the implementation of BPT automation are stressed throughout the course. All topics are supported by hands-on exercises designed to provide you with the ability to successfully automate using the BPT methodology.

Intended Audience

Test Automation Engineers who will be using QuickTest Professional and QualityCenter to implement automation in a Business Process Testing environment

Course Objectives

At the end of the course, you will be able to:

Perform Automation Tasks in the Business Process Testing Workflow
Define the role of the Automation Engineer in a Business Process Testing project
Create Application Areas in QuickTest Professional and associate object repositories, function libraries and keywords
Create a shared object repository
Create Keyword-Driven Components
Fulfill component requests
Use built in keywords and functions
Create custom keywords and functions
Convert business components to scripted components
Create new scripted components
Execute and debug test cases comprised of automated components
Apply best practices for the successful implementation of BPT automation
Prerequisites

Students taking this course should have:

Working knowledge of Windows
Basic understanding of the testing process
Completed Using QuickTest Professional training version 8.2 or greater
Completed Advanced QuickTest Professional training version 8.2 or greater
Course Outline

Working with business components
Creating and building business components
Requesting new components
Types of components
Creating and running business process test
Generating documents for BPT
Working with Parameters

http://www.crestechsoftware.com

An interactive process of concurrent product exploration, test design, and test execution. The heart of exploratory testing can be stated simply: The outcome of this test influences the design of the next test.

The plainest definition of exploratory testing is test design and test execution at the same time. This is the opposite of scripted testing (predefined test procedures, whether manual or automated). Exploratory tests, unlike scripted tests, are not defined in advance and carried out precisely according to plan. This may sound like a straightforward distinction, but in practice it’s murky. That’s because “defined” is a spectrum. Even an otherwise elaborately defined test procedure will leave many interesting details (such as how quickly to type on the keyboard, or what kinds of behavior to recognize as a failure) to the discretion of the tester. Likewise, even a free-form exploratory test session will involve tacit constraints or mandates about what parts of the product to test, or what strategies to use. A good exploratory tester will write down test ideas and use them in later test cycles. Such notes sometimes look a lot like test scripts, even if they aren’t. Exploratory testing is sometimes confused with “ad hoc” testing. Ad hoc testing normally refers to a process of improvised, impromptu bug searching. By definition, anyone can do ad hoc testing.

What kinds of specifics affect ET? Here are some of them:

1. the mission of the test project
2. the mission of this particular test session
3. the role of the tester
4. the tester (skills, talents, and preferences)
5. available tools and facilities
6. available time
7. available test data and materials
8. available help from other people
9. accountability requirements
10. what the tester‘s clients care about
11. the current testing strategy
12. the status of other testing efforts on the same product
13. the product, itself- its user interface - its behavior - its present state of execution - its defects- its testability- its purpose
14. what the tester knows about the product- what just happened in the previous test - known problems with it- past problems with it - strengths and weaknesses - risk areas and magnitude of perceived risk - recent changes to it - direct observations of it- rumors about it - the nature of its users and user behavior - how it‘s supposed to work - how it‘s put together - how it‘s similar to or different from other products
15. what the tester would like to know about the product

http://www.crestechsoftware.com