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

[BUG] SKIPPED tests seem to still be added to overall score results #687

Closed
agentpoyo opened this issue Mar 31, 2021 · 12 comments · Fixed by #1207
Closed

[BUG] SKIPPED tests seem to still be added to overall score results #687

agentpoyo opened this issue Mar 31, 2021 · 12 comments · Fixed by #1207
Assignees
Labels
8 pts bug Something isn't working sprint22.03 Sprint 22.03: January 27-February 9, 2022 v0.25.0 Issue included in v0.25.0 release

Comments

@agentpoyo
Copy link
Collaborator

Describe the bug
It seems that the SKIPPED tests are still being added in the total score results when running the CNF Test Suite.

When running a test, the total output displays a score total of 76 points but the final result states 86 points total. (see screenshot)

To Reproduce
Steps to reproduce the behavior:

  1. Follow common install steps to cnf-conformance
  2. Setup and use the sample-coredns-cnf cnf-conformance cnf_setup cnf-config=./sample-cnfs/sample_coredns_cnf/cnf-conformance.yml
  3. Then run a workload by doing LOG_LEVEL=error ./cnf-conformance workload
  4. See output

Expected behavior
The total points for SKIPPED tests should be removed from the totals in the final results.

These should also provide more information if SKIPPED. Perhaps 0 points of possible 10 points not counted.

Screenshots
image

Device (please complete the following information):

  • OS Linux
  • Distro Ubuntu
  • Version 18.04
  • Architecture x86
@agentpoyo agentpoyo added the bug Something isn't working label Mar 31, 2021
@lixuna lixuna added the sprint31 Sprint 31: April 8-21 (Pts: 26) label Apr 8, 2021
@wvwatson
Copy link
Collaborator

wvwatson commented Apr 8, 2021

@sishbi

@agentpoyo
Copy link
Collaborator Author

This one kind of leans and depends on https://github.com/cncf/cnf-conformance/issues/707

@williscool williscool self-assigned this Apr 22, 2021
@williscool
Copy link
Collaborator

This one kind of leans and depends on https://github.com/cncf/cnf-conformance/issues/707

@agentpoyo just noticed this. had been working on code for the solution. have you guys talked about this in a pairing session?

@wavell @denverwilliams ?

@lixuna lixuna added the sprint32 Sprint 32: April 22-May 5 (Pts: 44) label Apr 22, 2021
@williscool williscool removed their assignment Apr 23, 2021
@wvwatson
Copy link
Collaborator

wvwatson commented Apr 27, 2021

@lixuna lixuna removed sprint31 Sprint 31: April 8-21 (Pts: 26) sprint32 Sprint 32: April 22-May 5 (Pts: 44) labels May 10, 2021
@wvwatson wvwatson added the 8 pts label Oct 20, 2021
@HashNuke HashNuke self-assigned this Jan 17, 2022
@HashNuke
Copy link
Collaborator

HashNuke commented Feb 3, 2022

Verified issue with result score calculation.

  • Workload test says 149 of 296
  • Total points in the results yml file is 159 ((5pts * 30) + (10pts * 2) + (-1pts * 11) = 159)

The total score is 10 points less than what it should be. Screenshot below.
CleanShot 2022-02-03 at 17 02 26@2x

@HashNuke
Copy link
Collaborator

HashNuke commented Feb 3, 2022

The screenshot below are some notes from the workload test that I was running to validate the issue.

  • I made note of the tests that are failing or skipped.
  • Cross-verified the output on the console with the results yaml file.

Created tickets for any issues that were found during the validation exercise.

image

@HashNuke
Copy link
Collaborator

HashNuke commented Feb 4, 2022

Verified the points assigned to all tests and the behaviour for skipped tests. Compared the output on the console with the points assigned in the results yaml file.

  • Skipped tests that are prototypes or destructive are not listed in the results yaml file. I think they should be listed appropriately and marked as zero like the other skipped tests
  • ip_addresses test assigns 0 points for passing test. Will verify with the team that this is ok.

image

@HashNuke
Copy link
Collaborator

HashNuke commented Feb 4, 2022

Next: Will look into how the test score is calculated when outputting it on the console.

@HashNuke
Copy link
Collaborator

HashNuke commented Feb 9, 2022

  • Found two tests that are not defined in the points.yml file: insecure_capabilities and dangerous_capabilities
  • This accounts for the 149->159 difference.

image

@HashNuke
Copy link
Collaborator

HashNuke commented Feb 9, 2022

Found 7 skipped tests amounting to 40 points being included in the total maximum score.

non_root_user: 5
secrets_used: 5
prometheus_traffic: 10
open_metrics: 5
routed_logs: 5
tracing: 5
node_drain: 5

CleanShot 2022-02-09 at 17 07 54@2x

@agentpoyo
Copy link
Collaborator Author

agentpoyo commented Feb 10, 2022

Acceptance Criteria:

  • when running workload, I should see skipped tests not adding the overall points for categories.
  • I can see an example output here of skipped tests not adding to points total.

@agentpoyo
Copy link
Collaborator Author

687_skipped-tests

@lixuna lixuna added sprint22.03 Sprint 22.03: January 27-February 9, 2022 v0.25.0 Issue included in v0.25.0 release labels Feb 14, 2022
@lixuna lixuna closed this as completed Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8 pts bug Something isn't working sprint22.03 Sprint 22.03: January 27-February 9, 2022 v0.25.0 Issue included in v0.25.0 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants