-
Notifications
You must be signed in to change notification settings - Fork 4
Added Zephyr Squad Server support #10
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
base: main
Are you sure you want to change the base?
Conversation
|
Hi @crapitea! This is a massive update for the package. Thank you. I need some time to test code, complete the review and provide you with a feedback. |
nassauwinter
left a comment
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.
You have created a good functionality for Zephyr Squad here 👍
Could you please modify it according to my comments?
d651795 to
a7dcf81
Compare
ae33b2d to
001dced
Compare
0244e80 to
6d08887
Compare
6d08887 to
2d8ad1b
Compare
5b91e12 to
9494ac4
Compare
27c578b to
c5aa9ec
Compare
|
A number of modifications needed to be made based on the differences between Squad and Scale.
|
c5aa9ec to
cbceec3
Compare
cbceec3 to
61aadb2
Compare
|
Hello, guys. I was wondering how things are going with this PR and if there is anything I can do to help? So, can this PR be reviewed one more time, or do you need help with something to get things moving? |
61aadb2 to
3395237
Compare
At the present time the tox verifications should be resolved. The problem with that is that a decision should be made regarding how the function parameters should look. The Zephyr API uses camelCase instead of snake_case and considering the fact that not all parameters are documented, I decided that required parameters to use the same names like the ones in the documentation. This is a lot easier from a user's perspective since all parameters are the same as the ones in the documentation, but it's not pythonic. Solutions that I will implement in this PR to fix this:
|
3395237 to
a15f4cd
Compare
Can you also test this PR to make sure that everything is working as expected? For the moment, all needed modifications / blockers are fixed. |
5c7f79e to
2cdb4aa
Compare
|
@crapitea glad to hear it! |
2cdb4aa to
db6ae7c
Compare
fbf4c2e to
18c3d51
Compare
|
At the present time, everything needed was implemented to have support for the most commonly used functions of Zephyr Squad Server. Can you please review this and see if there is anything else that can be improved/reworked? |
48e2bfb to
9467feb
Compare
This commit introduces initial support for the Zephyr Squad (server) variant. Only a number of the available Zephyr API calls are introduced by this commit. All testing for this commit was done on a self-hosted Zephyr Squad instance.
|
@crapitea I also need support for the Zephyr Squad. How is this going ? |
|
There haven't been any update for this in quite a while. At the moment, this PR has to be rebased on the latest master to work as expected. However, I don't know if this functionality expansion is even wanted for this module, so until I know that this will be merged if all issues are resolved, I won't continue working on this. |
|
@nassauwinter Can you help here ? |
|
@tiagomendes7 For now, I've created a for of this repository that also has support for Zephyr Squad: https://pypi.org/project/zephyr-test-management/ |
This commit introduces initial support for the Zephyr Squad (server) variant. Only a number of the available Zephyr API calls are introduced by this commit.
All testing for this commit was done on a self-hosted Zephyr Squad instance.