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
ogr mock support for packit tests with unittest classes #310
Conversation
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
1 similar comment
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
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.
design LGTM
|
||
|
||
class ProposeUpdate(PackitUnittestOgr): | ||
datafile_github = "TestPropose_github.yaml" |
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.
these could be generated in the end, right? something like : TEST_DATA_TOP_DIR / test_file_name / test_class_name + ".yaml"
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.
@TomasTomecek you suggestion is to create trere another subdirectory for each "test file" and inside this have files for each testclass?
it is stored in tearDown function so it dumps data after every test.
update: adapted your suggestion and removed manual class name files handling
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
ogr 0.3.0 has been released. Let's re-run the tests. |
@jscotka please rebase to re-run the tests, thanks |
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
2 similar comments
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
There was an error while creating a SRPM. Output:
Return code: 1 |
There was an error while creating a SRPM. Output:
Return code: 1 |
There was an error while creating a SRPM. Output:
Return code: 1 |
There was an error while creating a SRPM. Output:
Return code: 1 |
There was an error while creating a SRPM. Output:
Return code: 1 |
There was an error while creating a SRPM. Output:
Return code: 1 |
There was an error while creating a SRPM. Output:
Return code: 1 |
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.
Please, try to use the current master version of OGR if it is possible.
If not, I'll create a follow-up for that...
There was an error while creating a SRPM. Output:
Return code: 1 |
1 similar comment
There was an error while creating a SRPM. Output:
Return code: 1 |
I'm trying to fix the issue so I'm using this PR for testing, please don't mind packit's comments |
It is not possible to do it without not nice workarounds. |
Congratulations! The build has finished successfully. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
I've force pushed after rebase bad data, need to do it again from proper computer |
move status from base test class to status test adapt PR suggestion for datafile path location for test classes
rebased to proper branch data |
replaces: #303
tested by command:
PYTHONPATH=. pytest-3 -v tests/integration_ogr_mock/
with version of ogr what support it.Update:
with local run tests works as charm.