Cancel
Showing results for 
Search instead for 
Did you mean: 

Collaborate & Communicate with Polarion ALM

Siemens Visionary Siemens Visionary
Siemens Visionary

 

 

Collaboration is critical for ALM Success

 

In today's software-driven world, collaboration & communication are fundamental components of software development and key pillars of modern application lifecycle management.

 

Collaboration amongst all members of the development team and executive decision makers is vital and traditionally can be problematic in siloed software development approaches. Polarion ALM aims to break down these barriers to facilitate collaboration & communication across all stages of the software development lifecycle.

To learn more about Polarion and how it can help to modernize your development toolchain through Collaboration, Traceability, Reuse, Interoperability and Automated Compliance, contact your Polarion sales advisor or better yet Test Drive Polarion ALM.

Comments
Experimenter

Polarion provides the option of using external testing tools and using Polarion as the central repository for tracking and reporting the results of testing. For example, you might use Eclipse TPTP for automated load and performance tests, and Selenium for automated user interface testing, importing results of every test execution to Polarion where the results are visible to stakeholders, and history of testing is maintained. You can use Polarion in this way with any external tool that can export test results to the xUnit XML format.

 

To integrate xUnit test results from an external testing tool with Polarion, you configure each of your external tools to write an xUnit file to a folder accessible to Polarion, and configure Polarion to periodically check each folder for the presences of a test results file. A scheduled job named xUnitFileImport is provided in Polarion which checks a specified folder, and if any file is found there, the test results it contains are imported to an automatically-created Selenium Test Run. The test results file is deleted from the disk so that the folder is empty, and will be empty until the external testing tool executes another round of testing and writes another results file to the folder.