August 2018 Summaries
4 posts from testRigor
Filter
Month:
Year:
Post Summaries
Back to Blog
TestRigor is a testing tool that uniquely identifies new functionalities in applications by focusing on changes rather than every line of code, allowing developers to pinpoint the source of new bugs. It offers a dynamic testing experience by executing actions similar to those of a user, such as clicking buttons and filling forms, while tracking previous test results. In a demonstration with a simple calculator app, TestRigor effectively detects and reports new functionalities, like the addition of a button, and provides descriptive reports with screenshots that highlight changes and actions taken. This capability enables developers to easily locate and address new features using identifiers like HTML IDs. Users are encouraged to explore TestRigor by signing up or requesting a demo to experience its practical application in their projects.
Aug 24, 2018
305 words in the original blog post.
testRigor is an automation tool designed to streamline regression testing by autonomously detecting new functionalities in applications and capturing screenshots to illustrate user actions and changes in the interface. Users begin by setting up a new application for testing, specifying various latency parameters to accommodate different network and server conditions. The tool explores the application by interacting with its elements and generating scenarios that represent potential user actions, including screenshots of each step. This process allows developers to identify and rectify issues, as demonstrated with a simple calculator application where a miscalculation was discovered through a retest. The tool highlights discrepancies by comparing past and present scenarios, making it easier for developers to locate and fix errors before they impact users.
Aug 23, 2018
873 words in the original blog post.
TestRigor is a test automation tool designed to enhance user experience on websites, exemplified by a demo for Mike's Bikes, by methodically exploring site functionality, clicking links, and capturing screenshots of user paths. Users begin by adding a new application in TestRigor, specifying details such as browser type and login credentials if needed. The tool offers customization options for test speed, including adjusting timeouts for server response, page load, and page rendering, which can be optimized for different network conditions or page complexities. Once configured, TestRigor's crawler navigates the website, identifying user-interactive elements like product links and checkout buttons, while generating screenshots to document each navigational choice. As changes are made to the site, the Retest feature allows TestRigor to detect and evaluate new functionalities, giving users the chance to review them as successful or identify potential bugs.
Aug 20, 2018
607 words in the original blog post.
In software testing, the term "code coverage" precisely refers to the percentage of code lines tested by automated tests, whereas "test coverage" lacks a singular clear definition and can vary in meaning. While some, including Martin Fowler and ThoughtWorks, equate test coverage with code coverage, an alternative perspective views it as a measure of how much of a feature set is executed by a test, often described as the "happy path." This latter definition focuses on expected user interactions rather than actual user behavior, making it challenging to assess the test's effectiveness in reflecting real software features. Therefore, it is crucial to clarify the definition of "test coverage" to ensure a shared understanding among stakeholders.
Aug 14, 2018
184 words in the original blog post.