SimVascular / SimVascular/svOneDSolver

Add code coverage

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

Nobody has claimed this yet.

enhancement good first issue
Dominant language
C++
Stars
22
Forks
27
PR merge metrics
No merged PRs in 30d

Description

Problem

We have integration tests (206732409d61fe91228d85fdc78f9527943726f3) and unit tests (4aac52ce70115d0274d99a54f2c69ad5fb928354) in this repository, but no information on code coverage.

Solution

Add coverage like we did in https://github.com/SimVascular/svMultiPhysics/commit/9c4598744e955778198eb861f61e1005b04b7f8b and https://github.com/SimVascular/svZeroDSolver/commit/06d92ed927329767f7c344b0bcd774bfd082504e

Additional context

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct and Contributing Guidelines

Contributor guide

Open the contributing guide

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

Review the unit-test commit 4aac52ce70115d0274d99a54f2c69ad5fb928354 and integration-test commit 206732409d61fe91228d85fdc78f9527943726f3, then compare the coverage setup in the referenced svMultiPhysics and svZeroDSolver commits. Add equivalent coverage reporting for this repository's tests; done means coverage information is produced for the unit and integration test suites.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.