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

.travis.yml (take 2) and test fixes #941

Merged
merged 20 commits into from Mar 26, 2013
Merged

Conversation

joshmoore
Copy link
Member

Changes for activating Python tests within .travis.yml. Primarily tests have been removed or fixed, though the use of OMERODIR in src/omero/cli.py was required for some tests. All tests pass locally, though some are still failing on travis. Opening PR to prevent conflicts in the test classes in other PRs.

Either due to the recent specification cleanup or due to
changes on travis-ci.org itself, the build is now passing.
Previous build with multiple TESTBUILD files
failed with out of space and other errors. Until
the build can be sped up and simplified, a simple
compile test (and for Python, unit tests) probably
suffices.
The move to argparse made many of the clitests unnecessary
since we no longer have our own `Arguments` class, or use
the `_likes()` method.
The ctx field for plugins was making undue use of the
OMERODIR global variable. These have been replaced by
a call to `_cwd(None)` which internally uses `self.dir`
which is usually initialized with `OMERODIR`. This makes
it possible to "re-home" a test.

With this change and the minor fixes to clitest/db.py
all of db.py is now passing.
Not using unittest.main() was causing sys.exit
not to be properly called on failures. Now a
helper method is available in xmlrunner.main
to "do the right thing".
@sbesson
Copy link
Member

sbesson commented Mar 25, 2013

Looks great! One hardcoded line used to define self.dir in db.py but this can be tackled somewhere else.
Ready to merge.

@joshmoore
Copy link
Member Author

For reference, dir = path(__file__) / ".." / ".." / ".." / ".." / ".." / ".." / "dist" # FIXME: should not be hard-coded at line 24 of clitest/db.py

@joshmoore
Copy link
Member Author

Added two minor commits, neither of which will have much code impact. Stylistic comments on ``README.md welcome.

/cc @hflynn

@hflynn
Copy link
Member

hflynn commented Mar 26, 2013

What is this docs/QUICKSTART.txt of which you speak?

@joshmoore
Copy link
Member Author

In the main repo under docs/ there's a file "QUICKSTART.txt" which shows developer-y types, more or less what to do to get started. This should likely be rationalized along with the "walkthroughs" under sphinx and various comments by @sbesson and @ctrueden (but elsewhere).

@sbesson
Copy link
Member

sbesson commented Mar 26, 2013

Actually, can we use Markdown relative path links there?

@hflynn
Copy link
Member

hflynn commented Mar 26, 2013

Ah, I see - yet another place you are hiding documentation! That should probably explain where the full docs are, but yes, not an issue for this PR.

@joshmoore
Copy link
Member Author

@jburel: nothing more from me if you're ok with merging.

jburel added a commit that referenced this pull request Mar 26, 2013
.travis.yml (take 2) and test fixes
@jburel jburel merged commit 8a2020a into ome:develop Mar 26, 2013
@joshmoore joshmoore deleted the travis-yml2-develop branch March 26, 2013 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants