Product Documentation
Getting to know accelQ
See all 11 articlesBuild your first automation Scenario
Application Environments and Configuring Data
Context and Views
- What is a Context
- Creating a Context
- Types of Contexts
- Synchronization
- Entry-Point Context
- What is a View?
Element Identification
- Adding Element to Repository
- Setting up Element Identification with Element Explorer
- Selecting appropriate attributes for element identification
- Handling dynamic elements
- Regular Expressions in Element ID
- Working with Repeat Elements
Actions and Logic Editor
- What is an Action?
- Creating an Action
- Sharing Action with other Contexts
- Defining Destination Context for an Action
- "Current Context" is not same as picking the actual name of the current Context
- Examples: Multiple Destination Contexts for Action
Action Logic by Examples
- Setting up synchronization in test logic
- Working with Repeat elements in logic editor
- How to loop on a set of repeating elements
- Working with large set of context menu items in your test application
- Working with family of dynamic, related fields (anchor element)
- Working with multiple browser tabs in test logic
Scenarios and Test Cases
- Create a Scenario
- Create Scenario Steps
- Data driven testing with Test Case concept
- Parameter Overriding
- Parameter Linking
- Comparing Global and Run Properties with Action Parameters
Test Suites
Local Agent: Execute Tests behind firewall
Execute Tests & Analyze Results
- Executing Tests in accelQ
- Browser Keep-Alive
- Overview of Test Report
- Perspectives in Test Reports
- Re-Run a test in accelQ
- Managing historical test reports
Change Management
API and Database Testing
Manual Scenarios and Test Cases
Running Manual Tests & Analyzing Results
Integrations & Extensions
- What is a User Extension
- Building a User Extension
- Integrating with Requirements Tracking Tools
- Integrating with Defect Tracking tools
- Supplying credentials for TFS integration (Requirements or Bug tracking)
- Jira Plugin for test coverage information
Automation Best Practices
- accelQ Best Practices
- What should constitute an Action?
- Parameterization Best Practices with Login Action Example
- Over Parameterization adds to maintenance effort
- Designing Actions for long term maintainability
- Designing Contexts for modularity
Administration
- User Setup
- Working with User Roles
- Manage Projects
- Project Admin - Status List
- Project Admin - Custom Fields
- accelQ On-Premise Server-Side System Requirements