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

CI: Code coverage does not include integration tests #3736

Closed
sssd-bot opened this issue May 2, 2020 · 1 comment
Closed

CI: Code coverage does not include integration tests #3736

sssd-bot opened this issue May 2, 2020 · 1 comment

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2695

  • Created at 2015-06-25 10:12:42 by lslebodn
  • Assigned to nobody

There is plan to extend integration test suite written in pytest.
We generate code coverage with the utility lcov + genhtml
but it does not include these tests.

Comments


Comment from lslebodn at 2015-06-25 14:32:46

Fields changed

component: SSSD => Continuous integration


Comment from jhrozek at 2015-06-25 15:52:13

Fields changed

milestone: NEEDS_TRIAGE => SSSD Continuous integration


Comment from jhrozek at 2015-07-20 22:23:45

Fields changed

rhbz: => 0


Comment from nkondras at 2015-10-02 15:22:50

I was also thinking about this. We can combine the "DEBUG" and the "COVERAGE" build and see how much longer a coverage-instrumented build takes to run through all the tests. Perhaps we can do that.


Comment from lslebodn at 2017-02-24 14:41:34

Metadata Update from @lslebodn:

  • Issue set to the milestone: SSSD Continuous integration
@andreboscatto
Copy link
Contributor

Dear Contributor/User,

Recognizing the importance of addressing enhancements, bugs, and issues for the SSSD project's quality and reliability, we also need to consider our long-term goals and resource constraints.

After thoughtful consideration, regrettably, we are unable to address this request at this time. To avoid any misconception, we're closing it; however, we encourage continued collaboration and contributions from anyone interested.

We apologize for any inconvenience and appreciate your understanding of our resource limitations. While you're welcome to open a new issue (or reopen this one), immediate attention may not be guaranteed due to competing priorities.

Thank you once again for sharing your feedback. We look forward to ongoing collaboration to deliver the best possible solutions, supporting in any way we can.

Best regards,
André Boscatto

@andreboscatto andreboscatto closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants