“Progress is impossible without change.” These are words spoken by Walt Disney, one of the most culturally influential men to walk the Earth. These are words that Qyrus personifies and that our amazing minds here live by. Change is what makes the world go round, and what keeps us writing these amazing Feature Fridays! This week we are joined by Tim, Jorell, and Linto to go over some changes that are coming to our main page’s dashboard. Let’s hear about how these changes can help you!
Well, for starters, the first thing you might notice is the update to the main dashboard. Previously, we were making little use of the available space on the dashboard. Now, we’ve changed that. You’re able to access information on passing versus failing rates across different projects, the total number of tests built and executed across the team, and a list of tests recently worked on.
Furthermore, we’re able to see daily contributions and login activity on a specific team, allowing team members to collaborate more efficiently. Users can also get a quick overview of their infrastructure setup. Lastly, on the page you’ll see we’ve added a checklist to keep track of things to-do.
And we’ve found that overall this update helps improve the user experience of the platform’s main dashboard, specifically in terms of navigation. We’ve moved the list of services from the main part of the page to be part of a collapsible side bar, now. That way, the most important things are in your face first.
Well, in general, there’s an impact in the area of reporting and analytics. There’s a lot more offered to the user to analyze the testing results across projects and teams. Instead of having to navigate all the way to a specific test’s report, we can view those details directly on the dashboard.
It gives us a better general overview of the testing ecosystem. We can specifically target Web projects, Mobile projects, or API projects on the dashboard. Overall, we can see how the amount of time viewing and analyzing a larger amount of reports might be impacted.
Adding more customizable widgets is one thing we’ve brainstormed, like providing more choices for the user to make the dashboard their own and tailor it to their needs.
For example, one user might not require such a large overview of an entire team or project, but rather something more granular. We want to enable users to customize their dashboard to help them become more efficient.
This is exactly where customization would come in handy! No matter what role you play, the dashboard can play to your needs. Testers and developers might quickly see the data on passing and failing rates in projects. But they also can get a quick view of the test infrastructure and its usage. Checklists also come in handy to keep track of tasks directly on the project.
Business technologists could use the dashboard for more business-oriented or managerial tasks such as checking on the health of projects and testing of various applications. They can also get a good overview of team contribution and activity.
Well, in general, I would give a better overview of operations allowing users to spend less time navigating around the platform to view specific reports and results.
A user can see the already recently worked on tests and in that way they can be prevented from recreating a test that is already existing. Then, they can just clone and reuse it.
Although nothing astronomical, these updates provide proof that Qyrus is an ever-evolving platform constantly looking to improve the lives and day-to-day of testers using it everywhere. And besides that, we’re committed to keep improving to help you achieve your testing goals more efficiently. Progress never stops, and neither does Qyrus. Thanks for joining us this week and we hope you enjoy the rest of your Friday!
Don't miss out on this must-attend event - mark your calendars for April 30th to May 5th, 2023 and join us at #STAREAST!
Performance profiling metrics on Qyrus enable testers to get a more granular view of how their API or APIs perform over time.
There have been a range of additions to mobile test building that make the process even simpler and more efficient. Learn More how you can improve your Mobile Testing with Qyrus.
The Xray integration is an out of the box integration that provides a link between your Xray issues and your Qyrus test scripts. Upon execution of these test scripts, the results are then populated straight to Xray to view execution results and updates from a single platform.
Low-code/no-code platforms can provide a wide range of benefits for teams in the testing industry. By identifying specific use cases, carefully evaluating different platforms, and implementing governance and security measures, teams can use low/no-code automation to improve their testing processes and achieve their goals
Testing an individual API is good but testing the functionality of multiple APIs together in a chain is an even better API testing strategy because that’s how APIs work in a real-world scenario.
CLI commands allow users to interact with, inspect, or execute automated test scripts without visiting the Qyrus UI. They have a range of functionality including allowing testers to execute scripts, update global variables, upload IPA/APK files, delete IPA/APK files, and send reports via email, all through pipeline.