Integrations

It would be great to support integration with Axe-watcher to be able to see accessibility related issues in Qase directly. https://axe.deque.com/

For better work on new software releases and the ability to build project documentation in terms of development and testing, I want to propose the addition of integration between Qase and Confluence. As it will positively impact the interaction between the development, testing and management departments.

We are migrating from TestRail and require our new test management platform to integrate with Jellyfish, which serves as our organization's single source of truth for all engineering metrics. This integration is critical for maintaining visibility and continuity in our engineering performance tracking. Our requirements for this integration include: Seamless data flow from the test management platform to Jellyfish to maintain our unified engineering metrics dashboard Real-time synchronization of test execution data, pass/fail rates, and test coverage metrics with Jellyfish Ability to track QE team productivity and testing cycle times within our existing Jellyfish engineering metrics framework Preservation of historical testing trends and performance data in our centralized metrics platform Integration of test automation metrics to correlate with our development velocity tracking in Jellyfish Jellyfish is already integrated with our Jira and Confluence instances, capturing development work and documentation. However, without test management integration, we have a critical blind spot in our engineering metrics. This gap prevents us from understanding the complete software delivery lifecycle and the true impact of quality engineering on our overall delivery performance. The integration must support our need to: Measure end-to-end delivery metrics that include both development and testing phases Identify bottlenecks between development completion and test execution Track quality trends alongside feature velocity in a single platform Demonstrate ROI of testing efforts through unified metrics reporting Enable data-driven decisions about resource allocation across development and QE teams As we transition from TestRail, it's essential that our new test management solution can feed data into Jellyfish to maintain continuity in our engineering metrics and reporting. This integration is a requirement for tool selection as Jellyfish remains our authoritative source for all engineering performance data.

Embed Figma links to a test case

Please add integration with Appium

Integration with Maestro Recently, we started using maestro ( https://maestro.mobile.dev/ ) to automate scenarios on mobile devices (Android and iOS). And for the centralization of all test layers of an application in Qase, the possibility of integration between Qase and Maestro is extremely important. I must inform the importance of implementing this resource due to the growing and constant demand from companies to use this tool for test automation on mobile devices and acceptance by the entire software quality community.

We have a large set of tests that we want to repeat (iterate) over different data sets. PHPUnit allows this via a Data Provider ( https://docs.phpunit.de/en/12.2/writing-tests-for-phpunit.html#data-providers ). However, the current Qase Parameter annotation for the phpunit reporter is a single value - which currently does not comprehend the dataset. This results in Tests using a data provider to show us "retries" rather than parameterized. Can we enhance the phpunit reporter to comprehend data providers? Something like the following example... Lets assume we have a test where we want to run it against several major versions. We may implement a data provider like... // Return a list of versions to test public static function getProviderData(): array { return [ 'v1' => ['version', 'v1'], 'v2' => ['version', 'v2'], 'v3' => ['version', 'v3'], ]; } #[ DataProvider('getProviderData'), Parameter('version', ''), Title("Test version") ] public function testVersion(string $paramName, string $version) { $this->assertStringContainsString('v', $version, "Version includes v"); } This would run "testVersion" 3 times, with $version = v1 | v2 | v3 respectively. In Qase, we would need that reported as a parameterized test Is this possible?

Clubhouse.io is Project Management Software similar to Jira. https://clubhouse.io/ It would be awesome to Integrate Qase with Clubhouse.io .

https://www.notion.so

Integration with AzureDevOps just like your Jira integration.