New feature added: Re-execute test executions

Abhimanyu Grover
January 1, 2016
This feature has been deprecated



Several times things go wrong during test execution or a new revision is committed by developers which renders testing useless. In such scenarios, you can now re-execute a test execution instead of creating it all over again.

Here’s how it works:

Step 1: Hover on test execution you wish to re-execute and click re-execute.
Step 2: Select statuses which you want to re-execute
Step 3: Execute cases

This feature can save you a great amount of time in creating duplicate executions.

‍

Related Posts

Model Context Protocol (MCP): A Guide for QA Teams
This article explores the integration of AI and ML models into software products, emphasizing the challenges faced by QA professionals. It introduces the Model Context Protocol (MCP), which facilitates seamless connectivity between AI models and external data. The post provides an accessible explanation of MCP, highlights essential knowledge for QA teams, outlines testing strategies for MCP-based systems, and showcases how tools like Test Collab can enhance the QA process.
Navigating Microservices: From Refactoring and Testing
In "Embracing the Microservices Revolution," explore a firsthand account of transitioning from monolithic to microservices architecture. Discover insights into the benefits and challenges of microservices, personal experiences with refactoring, and effective testing strategies to ensure smooth development transitions.
Hong Kong 2024 Cybersecurity Legislation: What You Need to Know
As of August 2024, Hong Kong has taken significant steps toward strengthening its cybersecurity framework, particularly focusing on critical infrastructure. This post explores the recent developments, legislative proposals, and the broader context of cybersecurity in Hong Kong based on a comprehensive research report.