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
Adds pulp-smash test for ansible remote #13
Conversation
126b1b2
to
1345079
Compare
1345079
to
a66807e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple small comments. Looks good!
.travis/install.sh
Outdated
| else | ||
| export PULP_SHA=$(curl https://api.github.com/repos/pulp/pulp/pulls/$PULP_PR_NUMBER | jq -r '.merge_commit_sha') | ||
| pushd pulp && git fetch origin +refs/pull/$PULP_PR_NUMBER/merge | ||
| git checkout $PULP_SHA && popd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mind breaking up these two lines onto multiple?
pushd pulp
git fetch origin +refs/pull/$PULP_PR_NUMBER/merge
git checkout $PULP_SHA
popd
.travis/install.sh
Outdated
| git clone https://github.com/PulpQE/pulp-smash.git | ||
| pushd pulp-smash && git fetch origin +refs/pull/$PULP_SMASH_PR_NUMBER/merge | ||
| git checkout $PULP_SMASH_SHA | ||
| pip install -e . && popd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
a66807e
to
db8e8d7
Compare
|
Presuming that you guys want to have unit tests running out of Unit tests have to be run by the larger Django project (pulpcore), since that is what possesses the information about the databases. Django therefore needs to be able to discover the the tests, which I don't think it can do unless they're nested inside the package (e.g. I've been trying to figure out a way around that with pulp_python, but haven't been able to thus far. If you do find a way, let me know. It's frustratingly inconsistent because, it does work that way for pulpcore, because manage.py can see the |
| def _gen_remote(): | ||
| """Return a semi-random dict for use in creating an remote.""" | ||
| return { | ||
| 'download_policy': 'immediate', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
download_policy and sync_mode are no longer a part of the base remote.
|
@daviddavis for the time being, my only suggestion is that you use the following layout for where your tests should reside:
In other words, rename the |
|
I'll update this PR based on the feedback. |
|
Regarding my previous comment, here is the solution I came up with. Nest In order to run unit tests, point the test runner directly at the unit test directory so that it doesn't detect the smash tests. In order to run the smash tests, point that test runner at the functional test directory so that it doesn't detect the unit tests. https://github.com/pulp/pulp_python/pull/151/files#diff-cd31ca8078680e1895d11f56d1fe38c2 Although like I mentioned earlier won't really matter until you get some unit tests. |
db8e8d7
to
418ab91
Compare
418ab91
to
61e0e48
Compare
No description provided.