This chapter covers the Polarion features that support quality assurance and testing activities. The main features and capabilities include:
Project templates pre-configured for test management projects. Templates include Work Item types to support testing, and provide for easy linking of test case and requirements artifacts for traceability and impact analysis. As with all project templates, templates with test management support can be customized and/or reused with modifications and customizations, after which users can create projects that have the desired custom attributes as defaults.
Test Specification, enabling both import of existing testing assets and artifacts from Microsoft Excel or Word, and creation of new testing artifacts. Choose a Document based approach, or a tool based approach, or a combination of both.
Test Execution and Automation. Create Test Runs comprised of references to sets of test cases (manual or automated). Execute Test Runs manually, or automatically, integrating JUnit tests with the Polarion Build system. Create Test Runs based on Polarion's Test Run Templates, or derive custom Test Run templates from these and create new Test Runs based on your derivative templates.
Parametrized Testing - Define Test Parameters in Test Cases, Test Runs and Test Run Templates that enable an abstract approach to test specifications, and efficient running of multiple testing scenarios when executing Test Cases.
Integrate with External Testing, either manually-executed or automated testing. Import results of external testing: import manually as needed, or automatically import results of external automated tests exported to the xUnit framework's XML format for test results. (xUnit export is supported by many third-party automated testing tools). Automatically create Defect type Work Items for developers when tests fail.
Excel Round-trip. Optionally use the Round-trip for Microsoft Excel feature to export Test Cases for external manual testing, and re-import test results stored in the Excel file, automatically creating Defect type Work Items for developers for failed tests.
Reporting of testing status and results. Configure standard dashboards, and use dedicated macros in custom wiki pages to create dedicated testing/QA report pages.
Polarion products with QA/testing support provide one or more project templates that provide support for creating, managing, and executing test cases. The project templates are pre-configured to provide Work Item types, link roles, and workflows that support quality assurance and testing. Some project templates may also provide support for defining and managing requirements, so that these may be easily linked to the test cases that verify them. This section briefly describes the QA and testing support provided in several project templates.
This section introduces the standard project templates that include quality assurance and testing support. For a complete listing of project templates with more detailed description, see User Reference: Default Project Templates.
Use this to template for projects emphasizing creating and managing software requirements and test case specification documents.
This template supports development of software requirements, risk management, and test management specifications. There is a variant of this template that has standard Java project structure set up for automated build process managed by Maven-2, enabling you to automatically run unit tests as part of the build process.
This template supports the full software application lifecycle based on a V-model process, including testing and quality assurance. There is a variant of this template that has standard Java project structure set up for automated build process managed by Maven-2, enabling you to automatically run unit tests as part of the build process.
This template supports the full software application lifecycle based on the SCRUM methodology, including testing and quality assurance. There is a variant of this template that has standard Java project structure set up for automated build process managed by Maven-2, enabling you to automatically run unit tests as part of the build process.
The best way to become familiar with these project templates is to work with a Polarion administrator to set up a "sandbox" folder in the repository in which you can create experimental projects from the different templates with QA and test management support. (For a list of the default project templates distributed with Polarion products, see User Reference: Default Project Templates.) Your administrator may give you permissions to create projects in this folder, or you may have to work with the administrator to actually create your experimental projects in the sandbox depending on your administration policy.
The procedure for creating projects is described in the Administrator's Guide. See Creating & Managing Projects: Project Administration. In your sandbox area, try creating a project with each of the foregoing project templates, selecting them on the relevant new project wizard screen. Note that you need to be using a license that provides the template(s) you wish to try. Keep in mind that you can always download an evaluation copy of Polarion to try the various project templates, as the evaluation license provides all of them. Remember too that any of the "stock" project templates can be customized, or have copies created which can be customized to suit your exact needs.
A project based on the "QA Project" project template has a space named Testing (under Documents and Pages in Navigation) which contains the following:
Document: Test Specification. This is a placeholder Document that you can optionally use to write up test case specifications. You can mark portions of the content as Test Case type Work Items which are then tracked in the tracker and managed with the project's workflow.
For information on working with Documents, see User Guide: Documents and Pages Topic.
Page: Test Case Traceability. This page is a comprehensive report that shows which Requirements have (and do not have) linked Test Cases.