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

Run tab shows green execution result after failed test run #2748

Open
JFoederer opened this issue Apr 11, 2024 · 2 comments
Open

Run tab shows green execution result after failed test run #2748

JFoederer opened this issue Apr 11, 2024 · 2 comments
Labels
analyze Analyze, Research or Investigate: solutions, complexity, reproducibility, ...

Comments

@JFoederer
Copy link
Collaborator

In RIDE's Run tab there is a colored view displaying pass/fail status and the active keyword during a test run. After the test runs ends I would expect this view to reflect the test run's final status. i.e. all green when all is ok, red when a fail was detected. This is in line with the default background color in the Robot test reports.

In the example below the run's first fail occurs during the final suite teardown. So, the test run failed, but all tests passed. In this situation the bar stays green after the test run, which is misleading:

image

Test suite used:

*** Settings ***
Suite Teardown    Fail    always

*** Test Cases ***
just one
    no operation

@HelioGuilherme66
Copy link
Member

@JFoederer Please experiment:, to see if is different:

  • Running the Test Suite Folder (maybe run without selected test cases)
  • Running the selected Test Case

@JFoederer
Copy link
Collaborator Author

Both have the exact same behavior.

@HelioGuilherme66 HelioGuilherme66 added the analyze Analyze, Research or Investigate: solutions, complexity, reproducibility, ... label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyze Analyze, Research or Investigate: solutions, complexity, reproducibility, ...
Projects
None yet
Development

No branches or pull requests

2 participants