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

If calling Stop Coverage for a page where Start Coverage is not called, logging of the keyword is wrong #3991

Open
aaltat opened this issue Jan 10, 2025 · 0 comments
Labels
bug Something isn't working priority: medium
Milestone

Comments

@aaltat
Copy link
Member

aaltat commented Jan 10, 2025

Describe the bug
If calling Stop Coverage for a page where Start Coverage is not called, logging of the keyword is wrong. In this case Stop Coverage keyword says that report creation was successful, even the report was not created. Instead keyword should log that report was not created, because coverage collection was not starter

To Reproduce

*** Settings ***
Library    Browser

*** Test Cases ***
Example
    New Page    http://www.google.com
    Stop Coverage

Expected behavior
Stop Coverage should say that report was not created because Start Coverage was not called for the currently active page.

@aaltat aaltat added bug Something isn't working priority: medium labels Jan 10, 2025
@aaltat aaltat modified the milestones: v19.3.0, v19.4.0 Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority: medium
Projects
None yet
Development

No branches or pull requests

1 participant