Project Description

GitHub Card:

The idea is put in place a test coverage tool like JaCoCo, JCov or Cobertura, connected to the java server and run the full test suite, to see which blocks of code are triggered. We already are using some test coverage tool for java unit tests, this card aims to be a spike to research about running Cucumber test with a test coverage tool.

Goal for this Hackweek

  • Find features not fully covered through our test-suite
  • Discover obsolete code (methods or classes), which are never triggered in any workflow.
  • Generate a map of features and files(or even piece of code that cover), with the idea of doing reverse engineering and be able to know which Cucumber feature can be broken when we merge a PR.


  • From one side we can improve our test coverage in the test suite to cover those functionalities in the suma server (spacewalk-java component) that we are not testing.
  • From the other side it will allow us to know (on suma-server code) which classes or methods are never triggered, helping to clean product code.

Looking for hackers with the skills:

susemanager test-coverage

This project is part of:

Hack Week 22


  • over 1 year ago: dgedon liked this project.
  • over 1 year ago: oscar-barrios started this project.
  • over 1 year ago: oscar-barrios added keyword "susemanager" to this project.
  • over 1 year ago: oscar-barrios added keyword "test-coverage" to this project.
  • over 1 year ago: oscar-barrios originated this project.

  • Comments

    • mariah9x
      about 1 month ago by mariah9x | Reply

      Good project! By identifying areas of code with insufficient test coverage, the project will enable improvements to the test suite mapquest, ensuring that all critical functionalities are adequately tested.

    • agelababypp
      14 days ago by agelababypp | Reply

      Java code exponentiation via square root Reasonably sized car engine with US area code 872 Not at all rough! papa's games