Test Planning
Structure and detail all your tests in a hierarchical tree. Add test steps, test parameters, and test configurations.
XORICON TestLab
Professional web-based test case management and requirement engineering software to improve product quality and track QA efforts
Develop Test Plan
Typical applications are too large to test them as a whole. To have an overview, divide your application under test into smaller units according to functionality by creating a test plan tree. By creating test subjects you hierarchically divide your application into units and sub units. After you define test subjects in the tree, you develop the tests to create for each subject.
Detail Tests
Detail your tests with built-in system attributes (e.g., type, status, priority, or person responsible) or create custom attributes of various data types. You can create custom workflow rules with field updates to set field values automatically (e.g., the date a test has been deprecated).
Design Test Steps
For each test create one or more test steps. Test steps contain detailed instructions on how to execute a test, the inputs to enter, and the expected outputs and results. Use rich text formatting to detail your steps, attach files, or discuss the instructions. You can also create custom fields and custom relationships on test steps.
Define Test Parameter
To increase the maintainability and flexibility of tests, you can add parameters to test steps. A test parameter is a variable that can be assigned a value outside the defining test. The use of parameters enables you to run the same test repeatedly each time with different test data or in a different environment. Before you can use parameters in steps you must define the parameter in the test.
Create Test Configurations
Create test configurations to set test parameter values. Each test configuration is a set of parameter values. Test configurations allows you to separate test logic from test data and to run a test multiple times, each time with different test data.
Requirements Coverage
One of the most important things of test management is requirements coverage. Requirement coverage allows you to track the relationship between your requirements and tests. With requirement coverage you can easily view the tests covering a requirements or you can recognize that a requirement has no associated test.
Test Execution
Create test instance by adding tests to test suites, schedule and run test instances. Analyze test runs and link issues.
Create Test Suites
As your application under tests changes, you run the tests to detect issues. In order to execute tests you create test suites. You can choose the tests to add to each test suite. Test suites can be organized in a hierarchical tree structure. You can assign a release cycle to a testsuite folder, therefore all test suites and their test instances will be automatically assigned to this release cycle.
Add Tests and Requirements
You can choose the tests to add to each test suite. This can be done directly by adding the tests or indirectly by selecting requirements. When you select a requirement all tests covering the requirement will be added to the test suite. Once you add a test to a test suite it will further be called test instance.
Add Test Configurations
Once you added a test or requirement to a test suite you can select the test configuration to be used for test execution. The test instances of a test suite are orded. You can reorder the execution flow. You can add the same test with same or different test configuration multiple times to a test suite.
Schedule Test Instances
You can control the execution order of test instances (tests) in a test suite. You can also schedule the date and time for executing a test and select the responsible user to execute a test. You can create custom fields and custom relationships e.g. to link the test environment for test execution.
Run Test Instances
When you run a test instance (test) manually, you follow the designed test steps and perform
actions on your application and compare
the expected results
with the actual outcome. You can execute a
test instance as many times as needed - each execution is a test run. If you execute a test instance multiple times in the same target release, the result of the lastest execution will be associated with the test instance. All test runs are linked to the test instance.
Link Issues
Issues (Defects) can be directly linked to test runs, test instances, test suites, tests, requirements, releases and cycles. Indirect links will be automatically created. E.g. if you link a defect to a test instance, a indirect link will be created for the test, the covered requirements, the test suite, the release cycle and release. This is essential for requirement to defect traceability.
Release Management
Define and analyze releases and cycles, link requirements and issues, and create release-based reports.
Define Releases and Release Cycles
Define a hierarchical release tree containing upcoming releases and cycles. A release represents a set of changes in one or more products that will be available for distribution. A cycle represents a development and quality assurance iteration to achieve a common goal, based on the release timeline.
Assign Requirements
Assign your requirements to releases and cycles. This lets you manage when and which requirements will be released. Requirement status and coverage fields give you a deeper insight into the release or cycle requirement maturity and test coverage.
View Detected and Fixed Issues
Issues can be linked to several entities, e.g., to requirements and releases. The release module allows you to display all issues detected or fixed in a release or cycle.
Analyze Releases and Cycles
You can generate graphs to obtain an deeper insight into your release or cycle. For a selected release or cycle, you can generate reports on linked entities such as requirements or issues, e.g., you can generate a report for the selected release displaying the related requirements, grouped by status and priority.
Requirements Specification
Structure and detail your project-related requirements in a hierarchical tree. Add documents, links, and comments.
Structure Requirements
The requirements tree is a graphical representation of your requirements specification, displaying the hierarchical relationship between different requirements. Each requirement in the tree has a unique ID, can be described in detail, and includes any relevant attributes, comments, or attachments.
Detail Requirements
Describe your requirements in rich text fields. Detail your requirements with built-in system requirement attributes (e.g., type, status, priority, or person responsible) or create custom attributes of various data types. You can create custom workflow rules with field updates to set field values automatically (e.g., the date a requirement has been deprecated).
Comments, Attachments, and Links
To collaborate with other users, you can add multiple comments to each requirement, allowing requirements to be easily discussed. The discussion will also be tracked. For each requirement in the requirement tree, you can add multiple attachments and links. All relevant data are stored in a central repository.
Trace Requirements
Requirements traceability defines a relationship between requirements. As requirements change, you can trace the impact of the changes. You can trace requirements affected by a requirement and trace requirements that affect a requirement.
Link Requirements
Requirements can be linked to several other entities, such as issues, releases, cycles, or user-defined custom entities. You can extend the business model by creating a new custom entity, e.g., "stakeholder". You can create a many-to-many custom relationship from requirement to stakeholder, allowing you to easily track the stakeholders for each requirement.
View Change History
You can view the change history for a selected entity. The change history includes all previous object versions. For each change, the name of the user who changed it, the change date, and the previous and new value will be automatically tracked.
Issue Tracking
Create incident, change, problem, service or feature request tickets and use custom worklists to view, filter, and prioritize.
Create and Assign Issues
Create incident, change, problem, service, or feature request tickets. Tickets can be assigned to users or groups. Every ticket has a status. Use state transitions and condition rules to implement your own workflow. Add documents, links, and attachments to add additional information, as well as add comments to collaborate with other users.
View and Filter Issues
You can use custom filter queries to filter issues, e.g., display issues assigned to you or last modified within the last month. Use the search filter on the right sidebar to add additional filter restrictions.
Link Issues
You can link issues to requirements, releases, and cycles or user-defined custom entities. An issue can be linked directly or indirectly to an entity. When you add a direct link to a cycle, an indirect link to the cycle's release will be created. Issue linkage is useful, e.g., to trace the defects of a requirement or to link a feature request ticket with its requirement .
Update Issues in Bulk
You can update one or more field values for multiple issues in table view. This is useful, e.g., to easily change the priority or status of multiple issues as a bulk operation.
Export to Spreadsheet
You can export your issues table view content to a spreadsheet. You can select the fields to export. After the export is created, it can be downloaded via hyperlink from the server.
Custom Views and Filter
Display data in tables, lists, trees, or tree tables. Each view can be customized and personalized.
Master Detail Views
Tree view allows you to display data in a hierarchical tree. The details of the selected record will be displayed beside the tree. Depending on the user permissions, relations and attributes are invisible, visible, or updateable. The tree can also be filtered by several criteria, e.g., to display requirements with status "Draft" or display issues of type "Service Request".
Editable Grid Views
Grid view allows you to display data in an editable hierarchical tree table. Depending on users' access permissions, you can easily create, update, and delete records. In the footer area of the table, you can select which attributes should be displayed.
Multi-join Table Views
Table view allows you to display data in a multi-column table. You can display records with associated links, e.g., display your requirements with assigned releases. If a requirement is assigned to multiple releases, the requirement will be displayed denormalized for each release.
List Views with Rich Text Columns
List view allows you to display data in a multi-lined table. This view is especially useful to display long and/or rich text fields, e.g., the multi-lined rich text requirement description. In the administration area, you can define your own custom lists using rich text fields and attribute references.
Custom Multi-join Filter Queries
For each view, you can select a filter query. A filter query consists of selections, one or more entities, restrictions, and sort criteria. The selections define which and how columns are to be displayed. The entities define the selectable columns. Restrictions can be complex expressions using nested Boolean expressions.
Fast-access Search Filter
You can use the search filter on the right sidebar to filter the results of the different views (tree, grid, table, or list) quickly and easily. Set the page size to specify how many rows will be loaded in one page (main area scrollbar). You can navigate to the next or previous page in the footer area.
Quick-Search and Auto-Suggestions
You can use Quick Search on the right sidebar to find records by name. Quick Search will immediately display matching records in a pop-up menu as you type.
Fully Customizable Data Model
Create unlimited new entities with custom fields and individual relationships between entities.
Unlimited Custom Entities
In addition to custom fields or relationships, you can define completely new object types equal to existing ones. Custom domain objects allow you to model specifics of your testing or enterprise domain, regardless whether you want to improve test integration or increase the quality of the information.
Add Custom Fields
You can create custom fields of different types, such as rich text fields, numbers, dates, and many more. Custom fields can be created for system and custom entities. You can customize screens by reordering fields.
Insert Custom Relationships
In addition to custom fields or custom entities, you can define custom relationships between arbitrary entities such as requirements, issues, or custom entities. These relationships allow you to model and administer detailed information about your business model or the application domain.
Customize Fields and Define Regular Expressions
You can customize entity fields, e.g., by modifying the set of options for drop-down-types, by making fields required or by defining regular expressions for text fields. This is particularly useful if you want to enforce your own naming policy.
Create Custom Applications
Custom entities and system entities can be combined into custom applications. Custom applications define a set of entities and relationships between these entities. Custom applications allow you to extend our application to support arbitrary use cases and administer data content extending far beyond the original application scope.
Workflows and Notifications
Specify your own workflow rules with custom email notifications and automatic field updates.
Create Workflow Rules
Workflow rules allow you to automatically send email notifications or update field values based on conditions that you define. Any time that changes to a data object meeting the conditions in a workflow rule, the application performs any workflow action associated with the workflow rule.
Add Email Notifications
A workflow email notification is a workflow action that sends an email according to a specified email template. Notifications can be sent to users, the application's user groups, or to anyone with a valid email address. Notifications will be sent when an object is created or edited and the associated workflow rule condition evaluates to true.
Add Automatic Field Updates
A workflow field update is a workflow action that updates a field value, based on an expression or formula. As an example, you can create a field update action that sets a custom field "expires" to "today plus one month" when an object of a specific type is created.
Create State Transitions
State transition rules can be applied to limit a user group's updating privileges on combo box elements. The state transitions for a user group define all valid workflow state transitions for that user group. As an example, you can define a state transition for a user group that defines that the issue status can only be updated from status "Fixed" to status "Closed".
Create Condition Rules
Condition rules can be used to modify attribute fields dynamically, e.g., declare fields as: required, editable, non-editable, or invisible; or, for combo box elements, define the selectable set of elements. With condition rules, you can, for example, define when an issue status is fixed; the field solution must be a required field. Additionally, combo boxes can be implemented whose selectable values are dependant on the selected value of another combo box.
Projects, Branches, and Baselines
Organize your data within projects. Create and use branches for different releases and freeze branches as baselines.
Select a Project
Use projects to enable multiple teams to work on different projects in parallel in the same application instance. For users working on multiple projects, it is possible to create cross-project views.
Create Projects
A project collects and stores data relevant to the application lifecycle management process. You can create an unlimited number of projects and use cross-project administrative settings (e.g., custom workflows and notifications) to configure all your projects.
Select a Branch
Use branches to enable your team to work in parallel on different development branches of the same project, e.g., if your business analysts want to update existing requirements for Release 2 while your developers are still implementing requirements of Release 1, you can create a new branch for Release 2, and your analysts can continue working.
Create Branches and Baselines
You can create new branches based on a predecessor branch to work in parallel and create baselines, if you want to freeze your requirements and tests on certain timelines. Baselines are read-only branches which enable you to keep track of changes made to your project over time.
Compare Records
You can easily compare the same records from different branches and baselines. It is also possible to compare different records from the same or different branches and easily update record values from older or newer versions.
Dashboards, Graphs, and Reports
Define custom graph and report templates. Arrange tables, lists, and graphs into personalized dashboards.
Create a Dashboard Page
You can create multiple dashboard pages. On each dashboard page, you can display graphs, tables, and lists side-by-side as dashboard elements. For each element, you can set an individual position and size. You can also define the user groups for which a dashboard page is visible.
Define Filter Queries
Create persistent filter queries for table, tree, and grid views. For each filter query, you can define complex restriction criteria, sort orders, and column selections. For each column, you can set width and alignment. You can also create filter queries joining to related entities, e.g., you can display requirements in a table with their linked releases.
Create Personalized Lists
Create personalized lists for list views. For each list, you can define which data should be displayed and how. You can use rich-text elements to build useful and aesthetically pleasing multi-lined lists. Each list can have up to five columns. You can set which user group members can use and see the list.
Define your own Graph Templates
You can create your own graph templates for custom and system entities. Graph templates let you view an image showing a graph describing the aggregated information from a filter query. For each graph template, you can define which fields will be grouped. For each graph, different views, such as pie chart, bar chart, and grid view are supported.
Create Graphs
For each system and custom entity, you can easily create real-time graphs by selecting a graph template targeting the entity. Many entities also support graphs on related data, e.g., you can select a release in tree view and generate a graph displaying the statuses of the requirements linked/related to the selected release.
Export Spreadsheet
For each entity, you can export the table view content to a spreadsheet. You can select the fields to export. After the export is created, it can be downloaded via hyperlink from the server.
Fine-Grained Permission Model
Manage users and user groups with a fine-grained and comprehensive permission model.
Create Users and Groups
Create new users and assign them to one or more user groups. You can invite new users via email or set an initial login and password manually. For each user, you can set an individual time zone and locale. Beyond built-in system user groups, you can create customizable user groups.
Set Application Permissions
You can define the applications and modules which you want to give a user group access to. When a user group member logs in, only authorized applications and authorized modules will be displayed, and records from unauthorized modules will be hidden.
Manage Entity Permissions
For each user group, you can specify which entities may be created, changed, and deleted. You can set these permissions for system entities, as well as for custom entities. To hide an entity for a user group, you can remove the module permission for this entity and user group.
Define Field Permissions
For each user group and entity, you can define which fields may be displayable and updateable. You can set these permissions for system fields, as well as for custom fields. Setting field permissions enables a powerful fine-grained authorization concept.
Set Action and Access Permissions
Action Permissions define the actions user group members can invoke, for example, you can define which user groups are authorized to send an email or export a spreadsheet. Access Permissions can be set on filter queries, dashboards, graphs, reports, and more. Objects of these entities will only be displayed to the objects' authorized user group members.
Product Tour
-
XORICON TestQA
Visionary application lifecycle management tool with reusable test cases and support for branching and baselining -
XORICON TestLab Professional web-based test case management and requirement engineering software to improve product quality and track QA efforts -
XORICON Requirements Powerful web-based requirement management tool to manage, organize, and track requirements, releases, and changes. -
XORICON IssueTracker Powerful web-based issue and ticket tracking system to easily manage, track and organize your tasks, defects and ideas. -
XORICON AppCreator Platform Platform to Build Your Own Business Application â Fast, Easy, and with Zero Coding