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

Testing project #249

Closed
orbitfold opened this issue Mar 6, 2015 · 2 comments
Closed

Testing project #249

orbitfold opened this issue Mar 6, 2015 · 2 comments

Comments

@orbitfold
Copy link
Contributor

The goal of this project is to ensure uniform test coverage of all TARDIS methods and functions. We use pytest for testing. The goal is to ensure 100% coverage. You can check coverage here https://coveralls.io/r/tardis-sn/tardis (note this does not include C function testing). The main challenge will be to test the C-part with pytest. The tests should run via issuing "setup.py test".

Before beginning of the program you should:

  • pick an untested function or two and write tests for them
  • [optional] write a test for some of the C functions in cmontecarlo.c/or cmontcarlo.h
    • an easy one can be rpacket_get_nu/rpacket_set_nu

During the program you will help the team making this code reach a coverage of close to 100% for both the python and c part

@unoebauer
Copy link
Contributor

@wkerzendorf - certainly still relevant. I guess also for GSoC 16.

@unoebauer
Copy link
Contributor

Deprecated - addressed by a dedicated TEP and the GSOC 2016 project of @karandesai-96.

Closing

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

No branches or pull requests

2 participants