November 2022 Summaries

In recent updates, enhancements were made to test case history management and table validation capabilities, alongside the introduction of new functionalities for HTTP request data collection and value grabbing in tables. Each single re-test now generates a unique execution link, preserving the history of test executions, which can be accessed via the Edit test case button. The Quick edit link allows script editing without navigating away from the current page. Users can enable the collection of browser HTTP requests through the settings menu, and detailed information can be accessed by clicking More details on the relevant step. New commands have been added to validate collective values in table rows or columns, such as checking the count, sum, average, and order of values, although these validations currently support only HTML-tagged tables. The grab command has been extended to allow users to grab multiple values from a table row or column, storing them as a JSON array string in a specified variable.

Regression testing and retesting are distinct forms of software testing that serve different purposes in the software development lifecycle. Regression testing is used to ensure that recent changes, such as new features or bug fixes, have not adversely affected the existing functionality of a software project, and these tests are typically part of an automated testing suite for efficiency and scalability. In contrast, retesting focuses on verifying that specific known bugs have been effectively fixed after updates, and it is performed on an as-needed basis rather than being integrated into a comprehensive automated suite. Understanding these differences is crucial to maintaining productivity and confidence within a team, and tools like testRigor can facilitate codeless test automation, making the process of creating robust functional tests straightforward and adaptable to changes.

A Quality Assurance (QA) Director plays a crucial role in ensuring that a company's products and services meet established quality standards by developing and implementing quality control policies, overseeing QA staff, and training new employees. Essential skills for a QA Director include leadership, communication, problem-solving, and an analytical mindset, with a solid technical background in the industry being necessary. Pursuing a career as a QA Director often starts with a degree in computer science or software engineering and involves staying updated with industry trends and best practices. Upon joining a new company, a QA Director should familiarize themselves with existing testing processes and collaborate with the QA team and key stakeholders to identify and address potential issues. This includes choosing the right test automation tools and continuously monitoring metrics to tailor testing strategies for organizational needs.

This tips and tricks session focuses on two main areas: the various deployment types and the accessibility of testRigor in testing or staging environments, as well as the straightforward creation of cross-platform tests for both web and mobile applications.