The dog days of summer, a time when it is so hot that even dogs lie around on the ground or in their dog houses, panting their breaths away. As heat waves stretch across the Northern Hemisphere, everyone is seeking shelter and relief from the sun. Relief comes in many fashions. Although we here are Qyrus do not offer relief from the heat, we do offer relief from those pesky test maintenance issues, which will hopefully tone down the heat and pressure of your releases! Today on Feature Friday, we will talk to Tim and Parth about what a global variable is on Qyrus and how it can help bring relief to your test automation issues.
Tell us more about global variables and its use cases.
Tim: Global Variables are things that store values that are used constantly or consistently across many test scripts. It helps testers maintain these values much easier. And, these values can be synthetically generated to ensure you are not creating a bias in your testing. Lastly, Qyrus allows the user to create multiple profiles. This allows for users to use the same variables but store different values for those variables.
Parth:
Imagine this… what if you are using a single value across dozens of test scripts and that value changes? Think of a URL, for example. Well, if you hard-coded the URL into every test script, you’d have a lot of work on your hands. However, you can put that URL to a global variable and just maintain it in one spot.
Tim:
Let’s be realistic, though, there are testers out there who deal with hundreds of test cases, let alone dozens. And with the ability to synthetically generate data, users can use them to test across large amounts of scenarios. You can synthetically generate names, numbers, emails, UUIDs, and much more.
Parth:
On top of that, the ability to create multiple profiles lets users test across multiple environments, such as a QA, staging, or dev environments. And honestly, the list of use cases can go on and on.
Wow, that’s a lot! They seem to have a wide variety of use cases along with many smaller complementary features that can help bolster testing. With all of those capabilities, we want to know more about how they might impact testing overall.
What is the overall impact on the testing process that is seen from global variable usage?
Parth:
Well, they would impact many things such as test building, execution, reporting, and maintenance. In terms of building, it makes it simpler in that you don’t have to constantly hardcode values into the script. For execution and reporting both, they allow you to test across different environments using the same script. And of course, maintenance is the primary impact.
Tim:
And in all those areas, the usage makes everything more efficient. You get wider test coverage overall, being allowed to synthetically generate data and test across multiple environments. And there’s a large amount of effort reduction.
Global variable is versatile in their usage. As you’ve heard, it can do many things, and have an impact in many areas of testing. Now that we know this, let’s learn more about how different personas might use this feature.
How might using global variables help testers, developers, and business technologists? What value can this feature bring?
Tim:
Well, with regards to testers, they could use this to generate data during runtime for usage in test scripts. They also can test against multiple environments such as a dev or a staging environment. And overall it would provide value in terms of maintenance.
Parth:
And a developer would get a similar value as a tester. For business technologists, it could help with their general understanding of test scripts, overall coverage, and maintenance of test scripts.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Tim:
Well, without Qyrus, a tester would have to have a high degree of coding skills and knowledge in order to not only write an automation framework but also implement these global variables. And even then, they would have to be able to synthetically generate data. That’s not a small task by any means.
Parth:
And other competitors of ours have similar functionality, but not the all-around functionality that we provide. Again, we can generate data for usage in runtime, and we have multiple environment profiles that can be created.
So, it’s not something that’s completely new, but it’s something that we here at Qyrus have taken and evolved into something better. We’ve added numerous capabilities and complimentary features that make them something that empowers testing every day.
How do you see this feature impacting day-to-day operations across organizations?
Parth:
Yes, as mentioned before, it really boils down to the maintenance aspect. It allows users to have a single point of maintenance for their values used across multiple scripts. And this obviously would have an impact on their day-to-day.
Tim:
And the fact that we can synthetically generate data means that testers no longer have to use some 3rd party tool to do so or they don’t have to hardcode random values into their tests every run. And the fact that you can use multiple profiles promotes the reusability of test scripts.
Well, hopefully, this Feature Friday has helped to cool your concerns on synthetic test data generation, managing data across environments, and more! Hopefully, this Feature Friday has convinced you to try out our Free Trial! With it being so hot out, we won’t keep you any longer. Enjoy the weekend and stay fresh during these dog days of summer!
All structure came from ideas. Whether it is the small business on the corner, your favorite celebrity social media account, or the donation center of your choosing everything was once run by a single or individual group of people. The same often occurs with application creation and testing. As the idea of an app is fostered, minimal resources are initially allocated to the creation and functionality of said idea or app. After the most viable product is achieved and functionality grows, so does testing complexity, time, and effort. This is why Quality Assurance teams exist. When applications of this scale and size become established within business processes it becomes increasingly tricky yet essential to test and maintain functionality, and therefore businesses allocate teams to doing so. This week’s feature Friday is brought to you by Milton and Adhi who will discuss exactly how Qyrus enables agile teams to improve collaboration within testing and Quality assurance.
Tell us more about How Qyrus enables collaboration and its use cases.
Milton:
Collaboration is embedded through all portions of Qyrus. During the process of test creation, each script can be tagged with custom and multiple simultaneous inputs. This means the tester, the sprint cycle, the release date, and the QA team member in charge can all be noted during script creation to maintain centralized data on the script that each team member can access.
Adhi: Furthermore, when the scripts are executed, the reports are hosted in Qyrus as a centralized reporting location, with value metrics, screenshots, and video evidence. But if these reports needed to be shared or saved separately, Qyrus also offers downloadable reports, PDF reports, and Email reporting capabilities. This allows for the maintenance of integral executions and data while making reports dynamic and readily shareable.
Milton:
Exactly, even when scheduling a test, you have the option to input an email. This allows for status updates and executive summaries that are triggered as desired but send reports and notifications straight to the user’s email. Couple this with the ability to note defects straight to Jira from reports as well, and it is obvious Qyrus enables quality assurance teams to be both agile and collaborative.
What is this feature’s overall impact on the testing process?
Adhi: Making testing teams more collaborative simplifies the testing process and leads to higher-quality application releases. With business analysts, developers, and testers on the same page, businesses can clearly establish and define application requirements, build and organize test scripts accordingly, and automate massive portions of their quality assurance and testing requirements.
Milton:
And with this transparency comes efficiency. Monitoring success, mitigating roadblocks, and producing high-quality applications, fast, require not only an agile methodology but also effective collaboration among all team members. Being able to keep all data centralized on Qyrus, while also making reports and execution data readily available through email, pdf, and downloadable reporting options, Qyrus enables clients with the best of both worlds giving teams maximum flexibility.
How might the collaborative nature of Qyrus help testers, developers, and business technologists? What value can this feature bring?
Milton:
We often see business technologists utilize this feature to take a step into testing. Because Qyrus is a low code no code solution that offers video and screenshot recordings of the test scripts, business analysts can follow the entire functionality and execution of the use case and test script while watching their application execute actions on video. Coupled with the collaborative nature of Qyrus, these users no longer need an instance or even to log into Qyrus but rather can digest these reports through email, PDF, or downloaded and maintained versions of test executions.
Adhi:
Testers also love Qyrus’s collaborative nature. Testers are often the most hands-on with the Qyrus solution but often struggle to relay testing information back to development and business-centric teams. We now see testers not only schedule executions on Qyrus but also their required outputs. That means every time a suite is scheduled so are the reports which will automatically be emailed out to all desired parties by the tester. Furthermore, any defects are logged straight from the Qyrus report to Jira or any other third-party defect management application allowing testers to send bugs and failed execution reports straight to the developer’s JIRA board with included screenshots, video, and execution evidence.
Milton:
Developers also use this functionality to ensure application coverage. Being built on a team-to-project structure, any members that are part of the team and project on Qyrus have access to all scripts, executions, and reports. This allows developers to access given projects and ensure the suite is covering the desired application functionality properly, that the sprints and regression tests are organized and built properly, and that executions are scheduled with reports populating required locations. Because nobody knows more about an application than its developer, Qyrus enables developers and testers to work as a unit, in tandem, to ensure functionality while maintaining the highest levels of test case coverage.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Adhi:
It may be the case that certain features are mirrored and certain functionalities exist outside of Qyrus to offer some collaborative solutions. What Makes Qyrus unique is not that there are collaborative capabilities, but that the platform itself was built to ensure the highest levels of collaboration. Utilizing collaborative features and capabilities across every aspect of testing allows Qyrus to not only offer collaboration but utilize collaboration to optimize the entire quality assurance lifecycle. Taking a team of individually intelligent developers and testers and coordinating to promote the highest efficiency and quality.
Milton:
Exactly, it is not as though Qyrus invented collaboration, but as a solution, Qyrus makes it that much easier for business technologists, developers, testers, heads of QA, and CTOs among others to impact the testing and quality assurance process. The more actively involved participants throughout the QA process the better, and Qyrus ensures all team members the ability to impact and monitor quality assurance effectively.
How do you see the collaborative nature of Qyrus impacting day-to-day operations across organizations?
Milton:
The collaborative nature of Qyrus is something we see utilized throughout organizations on a daily level. Whether it is the tagging mechanisms implemented every time a script is created, scheduling executions and automatic email triggers upon completion, or quick report-sharing options, Qyrus’ collaborative features are a highlight for users throughout daily testing tasks.
Adhi:
Exactly. It is not so much that the feature is something that is sought out and used every day, but more so a silent requirement. When collaborative features are being used properly, it is almost as if they are not even noticed. When clients are building scripts, throwing tags on them becomes second nature. Making sure everyone is on the email list when setting up a scheduled execution. These are not glamorous features but still provide immense impact, altering day-to-day actions to enhance and optimize the entire testing and quality assurance process.
Applications are taking over the business landscape. From client-facing applications that require a perfect user interface and an optimized user journey to internal applications that require efficiency and functionality to maintain business processes, testing, and quality assurance have never been more demanding. As businesses funnel resources into developing teams and research automation, note that one of the most important aspects to consider is collaboration. Having teams that can scale up and scale down as required, with a platform that centers around an organization and easy share options for executions and reports, Qyrus enables efficient and quality testing by promoting collaborative capabilities for agile test teams. That concludes this week’s Feature Friday, join us next week as we continue to discuss unique Qyrus features that optimize the quality assurance lifecycle.
Mobile testing is the process of validating any mobile application – Android or iOS, for desired functionality, consistency and usability. Mobile testing ensures that apps meet user expectations as well as business requirements
Utilizing a codeless, automated, AI and ML driven Mobile testing solution can improve Mobile application quality while increasing efficiency and reducing time to market.
In this video, we talk about:
What is Mobile Testing & how is it important?
Challenges to Mobile Testing
How can Qyrus help you with Mobile Testing?
Watch this video to learn more!
Qyrus partners with Chicago’s Agile Testing Days USA as a Gold Sponsor!
Save the date! Agile Testing Days USA returns to Chicago!
When: June 5th – 9th, 2022 Where: Chicago, IL
Agile Testing Days reaches out to all software engineers and testing professionals and the conference provides a fun platform to connect and network in the agile community.
Qyrus is an Agile Testing Days Gold Partner as we truly believe in the power of automated testing and event like these help us spread awareness about the future of testing. It also helps us connect with testers’ and developers’ communities.
Meet the Qyrus team at the event and learn how we are changing the testing world with our Codeless, Self-Healing, and Predictive Test Automation Platform. Learn from international thought leaders and software testing professionals about the recent trends in the testing world.
APIs are software intermediaries which allow two or more systems to talk to each other and interconnect. For this communication to be reliable, APIs need to meet the defined requirements for functionality & performance.
Utilizing a codeless API application testing can improve product quality, increase development cycle efficiency and expand test case coverage.
Comprehensively testing APIs can lead to desired functionality and performance, and dynamically transfer data between testing end-to-end API processes.
In this video, we talk about:
What is API Testing & how is it important?
Challenges to API Testing
How can Qyrus help you with API Testing?
Watch this video to learn more!
Gold Sponsors Booth #9 Join us in London this October for QA Financial 2022
Where: Hilton Canary Wharf
When: 18th October 2022
Software Risk Management and Technologies for Continuous App Delivery
Learn More About:
New standards for digital resilience Cutting edge automation for Devops and Transition management Test data management in the cloud Compliance and QA7
Speaker: Somnath Chakraborty Senior Vice President
Guest Speaker: Hameed Khairani Head of Systems Architecture, Shawbrook
Speaker Bio: Somnath heads UK and European business in Quinnox. He has more than 25 years of experience of which the majority has been in Financial Services. He is very passionate about solving complex problems with simple and easy to use technology and unlocking value for his clients.”
Topic: It’s a MAD rush Date: October 18th, 2022 Time: 12:00pm GMT Location: Hilton Canary Wharf
Description: Banks today are under increasing pressure to accelerate their digital initiatives to build the bank that customers need tomorrow. Modern Application Software Delivery has come to rely on cross functional Agile teams to rapidly deliver experiences for customers and intermediaries as well as the bank’s staff like underwriters and customer service representatives. Testing tools have not kept up with the required pace of agile while the market is full of fragmented point-solutions and maintenance-heavy frameworks.
The Qyrus team will outline how they use a Platform approach to unlock tremendous benefits across the full value stream of Modern Application Delivery. Additionally, a client will speak about how they’re using Qyrus to accelerate the quality delivery of their lending capabilities.
Platinum Sponsors Booth #3 Join us in Anaheim for STARWEST 2022!
When: October 2 – 7, 2022 | #STARWEST Where: ANAHEIM, CA + ONLINE
STARWEST returns, bigger and better than ever, to celebrate 30 years of testing quality and innovation.
This year, Qyrus partners with STARWEST as Platinum sponsors!
Enjoy Everything STARWEST has to offer:
Pre-Conference Training & Certification
Keynotes featuring recognized thought-leaders
In-depth half- and full-day tutorials
Concurrent sessions covering major issues and solutions
The Expo with the latest software testing solutions
Networking events
The Testing & Quality Leadership Summit & Women Who Test (in-person only)
Speaker Bio: Ameet Deshpande is an Engineering generalist and a builder at heart with a focus on Quality Engineering, Product Engineering, Product Management, cross functional team building and Agile.
He has been involved in many strategic initiatives at Quinnox and its clients and especially in Financial Services with primary experience in Quality Engineering, Cloud, SaaS, and AI. He was also involved in large scale transformation programs as part of a consulting & architecture groups within one of the top 10 Banks in the world. Ameet is an electronics & communication engineer by education with specialization in embedded systems and associated areas.
Topic: Testing as PaaS: Delivering on Speed, Quality, Collaboration, and Autonomy
Date: Thursday, October 6th, 2022
Time: 11:15am –12:00pm PST
Location: Disneyland Ballroom
Description: In the world of testing, fragmentation is increasingly a real challenge. Testing teams are faced with the paradox of choice every step of the journey from test design, test building, test data, test infrastructure, and test reporting. As organizations grow and scale, complexity in its testing landscape often leads to substantial overhead, inefficiency, and higher cost.
The trends in testing move toward automation and more collaboration between different functions as he importance of “customer experience” increases. While companies are responding to these macro trends, the real question is how long can they continue to do so with their fragmented setup before it puts increasing pressure on existing cost structures and more importantly impacts the quality of the customer experience.
This talk will introduce the audience to the concept of testing as PaaS which enables teams to run testing centrally and in a standardized way to eliminate fragmentation and enable co-creation, collaboration and reduce rework.
Topic: Upgrading API Testing Practices for Improved Testing Speed, Scale & Efficiency
Description: In the world of testing, fragmentation is increasingly a real challenge. Testing teams are faced with the paradox of choice at every step of the journey from test design, test building, test data, test infrastructure, and test reporting. As organizations grow and scale, complexity in their testing landscape often leads to substantial overhead, inefficiency, and higher cost.
This perfect storm of trends is creating a more acute and more urgent need to upgrade API testing practices and improve the testing speed, scale and efficiency.
Speaker Bio: Ameet Deshpande is an Engineering generalist and a builder at heart with a focus on Quality Engineering, Product Engineering, Product Management, cross functional team building and Agile. He has been involved in many strategic initiatives at Qyrus and its clients and especially in Financial Services with primary experience in Quality Engineering, Cloud, SaaS, and AI. He was also involved in large scale transformation programs as part of a consulting & architecture groups within one of the top 10 Banks in the world.
Moderator Bio: Rahul Thakur leads enterprise sales at Qyrus and is a technologist at heart. He has a background in consulting, technology, and private equity. He has been involved in several large scale strategic and technology transformation initiatives across multiple industries.
Web testing is a type of software testing that helps determine whether the functionality of a web application is working in accordance with the requirements. Just like any other software development, whenever changes are made to the application code, bugs can crop up somewhere in the application. Hence, they need to be thoroughly tested before releasing it to end users to enhance the overall user experience.
Utilizing a codeless, automated, AI and ML driven Web application testing solution can improve Web application quality while increasing efficiency and reducing time to market.
In this video, we talk about:
What is Web Testing & how is it important?
Challenges to Web Testing
How can Qyrus help you with Web Testing?
Watch this video to learn more!
Nobody likes doing the same things over and over again. That’s why some of the best inventions and innovations focus on making repeatable tasks simpler. Something like a dishwasher, whose prominence comes from the daily requirement of washing dishes. Another perfect example is a door buzzer. If you’ve ever lived in Chicago or most other cities, you are able to buzz people into apartment buildings to mitigate having to continually walk up and down stairs to invite guests in. This week’s Feature Friday explores a feature that is able to mitigate repeatable testing tasks, make maintenance easier, and enhance the overall testing and quality assurance process. This week, Suraj and Jorell will be discussing Qyrus’ execute test case action type, which allows users to execute a test script within a single test step. This allows for repeatable steps to be created into their own scripts and executed as a step within all required scripts.
Tell us more about the Execute Test Case feature offered by Qyrus, Its use cases, and its impact on testing and QA processes.
Suraj: The concept is actually fairly simple: anytime you have a set of steps that are repeatable throughout a test script, build those steps into a script and use the execute test case action type. This way, anytime those steps change, you can simply change and save one script, which will be reflected across all locations and implementations. It beats going through and changing every single script individually.
Jorell: Exactly the execute test case action type can be very handy. The example we often see is login scripts. You often need to login to test actions across an application, this way simply create one login script and input it as a step across all other scripts. Now step one of your given scripts will be “execute login” and the remainder of the script can continue accordingly.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Jorell: Without Qyrus we often saw developers storing versions of their reusable scripts on hand. These versions would then have updates per tweak and change to the code which quickly become libraries that became difficult to manage and maintain.
Suraj: Exactly, and beyond another library that needs maintenance the implementation of these blocks requires copying, implementing, and executing code. Qyrus provides a codeless solution where users can build and save scripts and attach them in as individual steps. All are housed and maintained by Qyrus, promoting ease of maintenance and overall test building efficiency.
What is the overall impact on the testing process when using Qyrus’ Execute test case feature?
Suraj: That’s a simple one, there is an overall increase in test-building speed. We often see clients use a base test case that can be anywhere from five to fifty steps long, acting as the stump of a tree, which, upon conclusion, allows for branches of tests to be created.
Jorell: Exactly and anytime there is a change to the base script, you can save that change across every branch in which it has been used or implemented. This form of reusability saves a multitude of man considering the resource requirement of having to go back and make the same change across all required test scripts. But beyond practicality, this feature also allows for best practices within test building.
How might the Execute Test Case feature help testers, developers, and business technologists? What value can this feature bring
Jorell: We often see testers using the feature to implement best practices and make testing more efficient. Going back and optimizing test cases to use this feature allows testers to simplify test case maintenance in the long run. Using embedded scripts allows for maximum reusability and ease of maintenance ultimately increasing the speed of testing.
Suraj: Similarly, developers also get greater insights on testing practices and can tailor suites against feature releases. If a specific feature is being developed, the base script can be simply navigating to that feature. By embedding that single script, developers can build tests for every facet of the desired feature creating a comprehensive, feature specific, test suite that can be executed throughout development and after release. This not only enables a shift left but promotes high quality application development.
Jorell: Also with simple drag and drop functionality, behind an already codeless and easy to use user interface, the feature requires minimal technical knowledge also enabling business technologists. Not only in the step building process, but even in reports and analytics compartmentalizing scripts allows for better organization and readability. Business technologists can easily take a foothold in the quality assurance process utilizing this feature, especially, within the Qyrus user interface.
How do you see the Execute Test Case feature impacting day-to-day operations across organization?
Suraj: Actually, leaning towards the opposite, this is a feature that mitigates daily requirements and actions. After creating an initial script, such as a login or navigation script, users no longer have to worry about rebuilding that process again across scripts. Furthermore, maintaining that process within a single location with a save across suite option becomes seamless. This not only saves time but more importantly, headache, when you have to go back and make a single change that exists across test scripts.
Jorell: Exactly, get rid of repeatable and unnecessary testing activities, and rather reuse test cases to save time, and maintenance requirements while promoting best practices. This feature not only impacts but enhances the daily testing process.
Having the ability to embed test cases as a test step is a versatile feature. It allows you to maintain lengthy test scripts, organize suites and scripts to certain requirements, and maintain base functionality of tests efficiently. All of these benefits among test building and maintenance enable efficient testing and quality assurance, and ultimately the release of high-quality applications. Don’t forget about next week’s Feature Friday, where we will continue learning more about Qyrus features, which help streamline automation across all application testing requirements.
Jerin Mathew
Manager
Jerin Mathew M M is a seasoned professional currently serving as a Content Manager at Qyrus. He possesses over 10 years of experience in content writing and editing, primarily within the international business and technology sectors. Prior to his current role, he worked as a Content Manager at Tookitaki Technologies, leading corporate and marketing communications. His background includes significant tenures as a Senior Copy Editor at The Economic Times and a Correspondent for the International Business Times UK. Jerin is skilled in digital marketing trends, SEO management, and crafting analytical, research-backed content.
