-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add 'metadata' parameters processing for Launch and Suite level #178
Comments
@petr-kus Please address this to Robot Framework |
? What are you talking about, they already have metadata and many things for the suite context. We of course just use their feature for suite Meta Data. (btw. it is almoste bug on your side becouse you take the suite atribute and move them to test atribute...) I don't see what can I request from Robot Framework site top of it. Maybe just make a system for test result storage as report portal or test archiver (btw. in test archiver it is possible to handle). Your system just can't sort all results of tests accordingly (becouse I can't tell that a group of tests have the same metadata and your system don't do it yourself). Roboto Framework don't support it at all, becouse they simply are not system for holding the resutls of tests. They are not interested in groups of suites. But your system is, it is one form primarly goals of your system. |
@petr-kus It looks like we missed Metadata attributes processing in our Agents. Then the issue should sound like "Add 'metadata' parameters processing for Launch and Suite level", rather than asking for adding additional parameters, which are completely not suitable in this case. NP, I'll add missed functionality in the next release. |
Is your feature request related to a problem? Please describe.
We now have many test suites in one launch. But we can't input the suite attribute. It is difficult to filter them and sort them.
Describe the solution you'd like
I would like to have available suite attribute settings the same way as launch attributes or tets attributes in parameters. At least.
Describe alternatives you've considered
I considered my client which would access the API of the report portal and set it. But it is an unsystematic approach and I think more people appreciate this feature.
I considered transferring these suite attributes to launch attributes.
But, attributes for launch are limited in length so can't be all attributes from the suite transferred to launch.
When there is too long an attribute you can't set it for launch (you give an error on API, level).
The text was updated successfully, but these errors were encountered: