Feature Friday – Discover the Benefits of CLI Commands
The pandemic instigated a range of lifestyle changes, as we all know. But as the situation becomes more contained and we see hopes of normality, we see reactions in these pandemic processes. That being said, there are many which have changed how we live. One of the most prominent is delivery services. What used to be ordering delivery for dinner after a long day has now extended to groceries, household items, pharmacy items among more. If you can name it, somebody will deliver it. But when diving a little deeper the concept is simple. By running a delivery service, the customer expends less resources, in this case time and effort, while yielding the same results, dinner. Meanwhile, the customer has the ability to utilize that time between ordering and delivery to do more. Qyrus CLI commands were developed in the exact same light. While tests are built on Qyrus, pipelines are essential. In the same way food or goods can be ordered and delivered, test scripts can be executed and returned without ever leaving your pipeline. This week’s Feature Friday is brought to you by Parth, and Steve who will tell you more about the benefits of CLI commands.
Tell us more about CLI command packages offered by Qyrus and its use cases.
CLI commands allow users to interact with, inspect, or execute automated test scripts without visiting the Qyrus UI. With a range of pipeline integrations out of the box and web hooks for required custom integration, these packages allow a range of functionality without ever leaving pipeline enabling Qyrus to execute in the background.
Exactly, and it goes beyond simply executing. CLI commands have a range of functionality including allowing testers to execute Qyrus Scripts, update global variables, upload IPA and APK files, delete IPA and APK files, and send reports via email, all through pipeline.
How do CLI commands impact the overall testing process?
CLI commands really optimize the test execution and reporting processes. Being able to handle a range of commonly required functionality, straight from a desired pipeline, with relayed reports. Centralizing execution and reporting while utilizing Qyrus automated test execution capabilities further optimize the testing process.
Exactly Qyrus adds features such as checking device availability, checking previous reports, seeing a list of all tests, seeing a list of all global variables, executions at a suite level, running the same test against multiple devices in parallel, among more. All of these capabilities are available within your, already existing, testing environment and pipeline creating a powerful synergy.
How might CLI commands help testers, developers, and business technologists? What value can this feature bring?
Testers are often the most well versed with our CLI commands. CLI commands come in handy when you have regression tests and suites that are being scheduled or triggered from a pipeline. In this scenario, the tester would have already developed scripts, even suites, using CLI commands across a range of functionality enabling the tester to leverage Qyrus capabilities. This makes testers lives simpler as required information is centralized.
Developers also utilize this feature and often build out logical pipelines and flows that are then filled by the tester. In essence developers can build out logical business processes that need testing on a given pipeline. After building out complex flows, testers or developers can associate the Qyrus executions with their accompanying pipeline executions, empowering the client straight from the pipeline.
Furthermore, business analysts can also utilize Qyrus to understand more about the testing lifecycle and the generation of large scale testing flows. Because there is no involved code, and these connections are a form like functionality, enabling business analysts to easily create flows and follow logical processes. After doing so, they have visual and data driven reports, with video and screenshots waiting for them on the other side. This feature brings together the entire testing team.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Other competitors don’t allow CLI commands on CI/CD tools. The usual case is executing CLI commands locally through the command prompt and working from there. With Qyrus, you don’t require learning anything different. These commands can be executed straight from pipeline and yield results accordingly.
Furthermore, there is the aspect of functionality. Outside of basic commands, such as executing tests, we also have a range of options including updating global variables, uploading IPA and APK files, among more, all while on the pipeline UI.
How do you see CLI commands impacting day-to-day operations across organizations?
This is a daily use feature as it can be applied anytime execution and update is required. The concept is simple, the more we can centralize the more efficient the testing process will become. In this case, taking the value of Qyrus and placing it behind CLI commands enables users to do more in a steadfast manner.
Exactly, the tester can test the application immediately after the IPA or APK file is finished building by uploading the file to Qyrus and triggering a test execution through their pipeline using the CLI commands. This unifies developing and testing into one flow, rather than a separated process and allows teams to shift left, and test earlier within the testing process.
CLI commands allow you to access the power and functionality of Qyrus in a range of different ways directly from pipelines and defect management tools. This enables more efficient testing where the foundation is Qyrus and relayed directly to the desired tool. Centralizing test data, minimizing learning curve, and adding an immense value set to an already existing system, Qyrus simplifies automated testing to optimize testing and QA lifecycles. Like food and grocery delivery services have impacted the daily dinner process, Qyrus impacts everyday testers, developers, and business analysts across day-to-day testing activities. Join us next week as we continue our dive into the Qyrus automated testing platform.