Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Soft Assertions in Cypress #29399

Open
veerpatil opened this issue Apr 24, 2024 · 1 comment
Open

Soft Assertions in Cypress #29399

veerpatil opened this issue Apr 24, 2024 · 1 comment
Labels
type: feature New feature that does not currently exist

Comments

@veerpatil
Copy link

What would you like?

Overview:
Soft assertions are a critical feature in test automation frameworks, enabling testers to continue executing test cases even after encountering failures, thus providing comprehensive insights into application behavior. As of the current version of Cypress, soft assertions are not natively supported. This feature request proposes the implementation of soft assertions within Cypress to enhance its capabilities and provide a more robust testing experience.

Problem Statement:
In traditional test automation frameworks, soft assertions allow testers to validate multiple conditions within a single test case, providing a more comprehensive understanding of application behavior. However, Cypress lacks native support for soft assertions, limiting testers' ability to perform such validations effectively. Presently, encountering a failed assertion in Cypress halts the test execution, preventing subsequent assertions from being evaluated within the same test case.

Proposed Solution:
Introducing soft assertions in Cypress would involve enhancing its assertion mechanism to handle failures gracefully without terminating the entire test execution. This enhancement would allow testers to continue evaluating subsequent assertions even after encountering failures, thereby providing a more detailed report of test results. Additionally, incorporating a mechanism to aggregate and report all failed assertions at the end of the test execution would further improve test visibility and debugging.

Why is this needed?

In traditional test automation frameworks, soft assertions allow testers to validate multiple conditions within a single test case, providing a more comprehensive understanding of application behavior. However, Cypress lacks native support for soft assertions, limiting testers' ability to perform such validations effectively. Presently, encountering a failed assertion in Cypress halts the test execution, preventing subsequent assertions from being evaluated within the same test case.

Other

No response

@jennifer-shehane jennifer-shehane added the type: feature New feature that does not currently exist label Apr 24, 2024
@migueldsol
Copy link
Contributor

Hello @jennifer-shehane . I've been exploring this feature and was wondering if you were open to implementing it into Cypress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature that does not currently exist
Projects
None yet
Development

No branches or pull requests

3 participants