Home / Companies / testRigor / Blog / October 2022

October 2022 Summaries

13 posts from testRigor

Filter
Month: Year:
Post Summaries Back to Blog
Recently, a new feature was introduced that allows for data set connectivity to baseline mutations triggered by CI tools. This enhancement enables users to connect data sets to test cases through an API call from their CI tool, utilizing a newly added field named datasetName in the testCase structure of the baseline mutation API. This field facilitates linking a test case to a specified dataset, improving integration between test management and data handling processes.
Oct 31, 2022 73 words in the original blog post.
The October testRigor Newsletter highlights new features, sessions, and resources aimed at optimizing test automation with testRigor. It invites users to participate in bi-weekly Tips & Tricks sessions led by CEO Artem Golubev, covering topics such as implementing testRigor on-premise and building cross-platform tests for web, Android, and iOS. The newsletter also promotes a webinar on assessing the ROI of no-code test automation, offering insights into effective metrics and case studies. New articles on topics like visual validation, BDD frameworks, and best practices for testRigor are featured in the blog section. Recent feature updates include options to save downloaded files as variables, accept browser alerts or prompts, and take OS-level screenshots in non-headless mode, with detailed descriptions available to paid customers via Zendesk.
Oct 31, 2022 617 words in the original blog post.
Web automation tools traditionally rely on locators such as id, name, or XPath to identify web elements, but the dynamic nature of modern web development has made XPath increasingly popular due to its flexibility in navigating HTML and XML structures. Absolute XPath, which starts from the root, is less advisable due to maintenance difficulties, whereas relative XPath offers a more concise and adaptable alternative by using attributes like id or class. Various methods, including contains(), and(), or(), not(), text(), and starts-with(), enhance XPath's ability to handle dynamic elements. XPath axes, such as ancestor, child, and descendant, provide further navigation capabilities within the document structure. Despite its widespread use, XPath can lead to test failures if there are changes in the element hierarchy. Modern automation frameworks like testRigor bypass these limitations by analyzing multiple locators, significantly reducing test maintenance and enhancing stability by allowing users to refer to elements as they appear on the screen, without the need for specific locators.
Oct 26, 2022 1,600 words in the original blog post.
Regular expressions, or Regexes, are powerful tools used to describe text patterns and are commonly employed by developers and data professionals for efficiently handling and modifying large quantities of text. Despite their complexity, this cheat sheet aims to simplify Regex usage by providing foundational knowledge and examples, such as matching phrases with specific patterns. Regexes are versatile in finding word positions, identifying text with specific HTML tags, and searching large datasets like log files or computer folders. Most modern programming languages, including Java, JavaScript, Ruby, Python, and Perl, have built-in Regex support, with each offering unique functionalities to enhance text processing capabilities. The guide also includes a comprehensive reference of Regex symbols, quantifiers, character classes, groups, ranges, and special characters to help users write effective expressions. Additionally, resources for advanced learning and understanding what constitutes a good Regex are recommended, particularly for users of specific programming languages like Python.
Oct 21, 2022 931 words in the original blog post.
The webinar explores the benefits and challenges of implementing no-code test automation within organizations, emphasizing the importance of selecting the right tools due to the diversity in available features. It addresses the growing interest in no-code solutions by highlighting three methods for evaluating the return on investment (ROI) of these tools. Additionally, it provides guidance on essential metrics to monitor and includes a detailed walkthrough of a case study to illustrate successful implementation and outcomes.
Oct 17, 2022 115 words in the original blog post.
A recent upgrade to the reusable rules functionality allows the use of dynamic values, enabling users to integrate stored values into their automated processes more efficiently. The update provides flexibility in defining variables within rules, using quotation marks or arrows, and allows direct insertion of values or referencing previously stored variables. Additionally, the upgrade includes enhanced mobile functionality, allowing users to interact with Android and iOS devices by executing commands to tap the Home button and access recently opened apps, although similar functionality for iOS's recently opened apps is still under development.
Oct 17, 2022 189 words in the original blog post.
Many companies struggle with achieving high automated test coverage, with the industry average for end-to-end test coverage in 2022 being under 30%, primarily due to the extensive time and resources consumed by test maintenance. With around 350 tests, a full-time engineer's time is often entirely devoted to maintaining these tests, hindering the possibility of reaching 100% test automation. Recent trends in no-code and codeless tools, such as record-and-playback solutions, offer an alternative by allowing individuals without coding experience, including QA personnel and team members with non-engineering backgrounds, to create and execute tests. These tools aim to simplify the creation and maintenance of automated tests, potentially enabling organizations to achieve their desired automation coverage more efficiently.
Oct 17, 2022 181 words in the original blog post.
Smoke testing is a vital initial step in software testing that aims to determine whether a software build is stable enough for further, more detailed testing stages. Originating from practices in the electrical industry, where devices were checked for smoke upon first use, smoke testing in software involves verifying core functionalities to detect major issues early, thus saving time and resources. It is a subset of acceptance testing, conducted immediately after a software build is created, and can be done manually, automatically, or through a hybrid approach. Its primary benefit is identifying critical blockers early, which reduces the cost and effort of later testing stages. Smoke testing is especially beneficial for complex applications, such as e-commerce or banking platforms, where engaging the full QA team without prior verification could lead to inefficiencies. Automated tools like testRigor can enhance smoke testing by allowing test cases to be written in plain English and integrating seamlessly with CI/CD pipelines, offering clear reporting and minimizing manual intervention.
Oct 15, 2022 1,343 words in the original blog post.
The session outlines nine best practices for utilizing testRigor, aimed at enhancing the stability, reliability, and maintainability of tests. By adhering to these practices, users can create tests that are not only more robust but also easier to manage and execute, thereby improving the overall testing experience.
Oct 14, 2022 31 words in the original blog post.
testRigor is a versatile tool that enables manual QA teams, business analysts, and product managers to create executable specifications in plain English, eliminating the need for QA automation engineers. It empowers anyone in the company, regardless of technical expertise, to write tests, making it accessible for roles like customer success and sales. testRigor also facilitates the hiring process by connecting businesses with certified testRigor users, allowing companies to evaluate potential hires through real-world test creation on production systems.
Oct 13, 2022 146 words in the original blog post.
Behavior-driven development (BDD) is a method that aligns product development with customer expectations by focusing on identifying and automating expected system behaviors. This approach simplifies collaboration between technical and non-technical team members by using scenario-based outlines, which guide developers and testers. Several BDD tools are available, each with unique features and requirements. Cucumber, JBehave, Behat, and SpecFlow use the Gherkin language to define behaviors, requiring programming knowledge for implementation, while testRigor offers a more accessible approach with plain English scenarios interpreted by an AI engine, eliminating the need for coding. Choosing the right tool depends on the team's specific needs and technical expertise, with testRigor being a notable option for its ease of use and minimal maintenance.
Oct 07, 2022 1,266 words in the original blog post.
testRigor is a versatile tool that caters to companies of all sizes, from small teams to large enterprises like Netflix, aiming to accelerate the achievement of QA automation goals and significantly reduce test maintenance efforts.
Oct 05, 2022 52 words in the original blog post.
testRigor has introduced several new features to enhance its testing platform, including the completion of the third phase for Chrome Extensions, which can now be used without opening them in a new tab. Users need to upload a .crx file in the settings to enable and activate extensions in test cases, ensuring the name matches the one in the Integrations tab, and must disable incognito mode. A new Test Case Page allows users to edit and view versions of test cases from all runs, while the copy feature facilitates transferring test cases between suites along with their rules and data. Additionally, geolocation settings for desktop browsers are now available for Ubuntu Chrome, Windows Chrome, and Windows Edge, expanding from mobile testing, and new devices like the iPad (2020) and iPad Mini (2019) have been added. TestRail integration improvements allow customization of the TestRail Run Name on the run page or via API, defaulting to testRigor's value if unspecified.
Oct 03, 2022 321 words in the original blog post.