Skip to content

Unit testing for easyconfigs#228

Merged
boegel merged 9 commits intoeasybuilders:developfrom
boegel:unit_testing
Apr 23, 2013
Merged

Unit testing for easyconfigs#228
boegel merged 9 commits intoeasybuilders:developfrom
boegel:unit_testing

Conversation

@boegel
Copy link
Copy Markdown
Member

@boegel boegel commented Apr 23, 2013

This introduces unit tests for easyconfigs.

With n easyconfig files, n+1 tests will be run, i.e. each easyconfig file will be parsed and an easyblock instance will be created for it, and a full dependency graph is built.

Example run:

$ python -m easyconfigs_test.suite
WARNING: xmlrunner module not available, falling back to using unittest...

.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
----------------------------------------------------------------------
Ran 953 tests in 55.632s

OK

@JensTimmerman
Copy link
Copy Markdown

JensTimmerman commented Apr 23, 2013

Should this not be in easybuild/test ? (with an extended path in all __init__.py files there)

@JensTimmerman
Copy link
Copy Markdown

JensTimmerman commented Apr 23, 2013

or easybuild/easyconfigs/test if you want to be consistent...

@JensTimmerman
Copy link
Copy Markdown

JensTimmerman commented Apr 23, 2013

But maybe a better solution would be to put all testcases in /test in each repo?

@boegel
Copy link
Copy Markdown
Member Author

boegel commented Apr 23, 2013

Initially, I put it into easybuild.easyconfigs.test, but then I changed it so it wouldn't force me to transfer the easybuild and easyconfigs dirs into packages in this repo.

@boegel
Copy link
Copy Markdown
Member Author

boegel commented Apr 23, 2013

Putting everything in /test is also something I was thinking of, i.e.:

  • test/framework
  • test/easyblocks
  • test/easyconfigs

The downside is that this will move the unit tests to a different location in the framework repo... Which is OK if we make it explicit, I guess, it doesn't affect the eb functionality.

@boegel
Copy link
Copy Markdown
Member Author

boegel commented Apr 23, 2013

Reorganized easyconfig tests in test/easyconfigs, also doing it for the other repos.

@boegel boegel mentioned this pull request Apr 23, 2013
Merged
@boegel
Copy link
Copy Markdown
Member Author

boegel commented Apr 23, 2013

Also moved the unit tests for the other repos, see easybuilders/easybuild-easyblocks#178 and easybuilders/easybuild-framework#611

@JensTimmerman
Copy link
Copy Markdown

JensTimmerman commented Apr 23, 2013

excellent

boegel added a commit that referenced this pull request Apr 23, 2013
@boegel
Merge pull request #228 from boegel/unit_testing
ec2d85c 
Unit testing for easyconfigs
@boegel boegel merged commit ec2d85c into easybuilders:develop Apr 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

v1.4.0

Development

Successfully merging this pull request may close these issues.

2 participants

@boegel @JensTimmerman