Add coverage

[sseraj]

Purpose

Added codecov coverage

Type of change

What types of change is it?
Select the appropriate type(s) that describe this PR

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@26916e2). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head e12cfb4 differs from pull request most recent head fb4038e. Consider uploading reports for the commit fb4038e to get more accurate results

@@            Coverage Diff            @@
##             master      #48   +/-   ##
=========================================
  Coverage          ?   76.37%           
=========================================
  Files             ?        3           
  Lines             ?      364           
  Branches          ?        0           
=========================================
  Hits              ?      278           
  Misses            ?       86           
  Partials          ?        0           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 26916e2...fb4038e. Read the comment docs.

[ewu63]

Okay I think the coverage is 0 because we are running subprocess.run which spawns a subprocess, meaning coverage.py can't really track what's going on. Perhaps this is the time to actually convert examples to tests so we run them within the same python process?

[sseraj]

I just tried running a basic test locally and can confirm that the issue is with subprocess. I'll work on converting the tests. Should I make a separate PR? This will also require some changes to cgnsUtilities.

[marcomangano]

Yeah I think a separate PR makes sense, then we just merge master here and hope that everything works as it should

[anilyil]

Is this ready for review or are we waiting for #54?

[ewu63]

Is this ready for review or are we waiting for #54?

Yes #54 has to be merged first.

[ewu63]

This is no longer needed