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

First setup experience is confusing #345

Open
kilianc opened this issue Jul 14, 2018 · 1 comment
Open

First setup experience is confusing #345

kilianc opened this issue Jul 14, 2018 · 1 comment

Comments

@kilianc
Copy link

kilianc commented Jul 14, 2018

We're setting up our code coverage for a monorepo with multiple apps running their own test suites in parallel inside a container.

We're working on a feature branch and we have no visibility on codeclimate because nothing has been merged to develop/master yet (no code coverage on master). We can not merge our PR until we can QA and make sure everything works according to plans.

Is this a side effect of misconfiguration or expected behavior?

Also, we're mounting a volume to write the reports on the host and it is unclear how to fix the paths. The approach so far has been: sed -i "s|/opt/app|$root_dir/$app|g" $coverage_path/$app/coverage/lcov.info

@kilianc
Copy link
Author

kilianc commented Jul 14, 2018

For example, given this data / project structure, does this look ok?

{
  "blob_id": "a7df2...a0",
  "coverage": "[null,null,1,1,1,1,null,1,null,1,7]",
  "covered_percent": 100,
  "covered_strength": 1.8571428571428572,
  "line_counts": {
    "missed": 0,
    "covered": 7,
    "total": 7
  },
  "name": "apps/foo/lib/something.js"
}
apps/
├── bar/
├── boo/
├── far/
└── foo/
    └── something.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants