omallassi / omallassi/adrust

Check if / how to integrate cucumber tests into coverage

Open
#29 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

code quality enhancement help wanted
Dominant language
Rust
Stars
21
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Following would be to use cargo-kcov. it was a test to integrate cucumber tests but it seems like kcov fails while reading cucumber

extract from https://travis-ci.org/omallassi/adrust/jobs/652901336

cargo-kcov 0.5.2
2836    Coverage found the following executables: ["/home/travis/build/omallassi/adrust/target/debug/adr_search-b83ba7d78b9cb9a6", "/home/travis/build/omallassi/adrust/target/debug/create_adr-600ddbd55dcf1721", "/home/travis/build/omallassi/adrust/target/debug/adr-54c7196f98ac1e56", "/home/travis/build/omallassi/adrust/target/debug/adr_config-ef1e10ed339cb571", "/home/travis/build/omallassi/adrust/target/debug/adr_core-fb277a0cdad7dd02"]
2837     Running "kcov" "--exclude-pattern=/home/travis/.cargo" "--verify" "/home/travis/build/omallassi/adrust/target/cov/adr_search-b83ba7d78b9cb9a6" "/home/travis/build/omallassi/adrust/target/debug/adr_search-b83ba7d78b9cb9a6"
2838
2839running 0 tests
2840
2841test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
2842
2843     Running "kcov" "--exclude-pattern=/home/travis/.cargo" "--verify" "/home/travis/build/omallassi/adrust/target/cov/create_adr-600ddbd55dcf1721" "/home/travis/build/omallassi/adrust/target/debug/create_adr-600ddbd55dcf1721"
2844No such file or directory (os error 2)
2845There was an error parsing "./features/adr_lifecycle"; aborting.
2846error: failed to get coverage
2847caused by: exit code: 1

The following coud be happened to .travis.yml

    &&
    sudo apt-get install cmake g++ pkg-config jq &&
    cargo install --force cargo-kcov &&
    cargo kcov --print-install-kcov-sh | sh &&
    cargo kcov -vV &&
    cargo kcov --verbose --coveralls --all --no-clean-rebuild &&
    echo "Uploaded code coveralls via cargo-kcov"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the failing Travis CI output and inspect .travis.yml, especially the proposed cargo-kcov commands. Reproduce the failure around features/adr_lifecycle and determine whether cargo-kcov can process the Cucumber tests. Done means a documented or working Travis coverage integration that includes the Cucumber tests without the reported parsing error.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ci-cd, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.