We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.Describe the bug Mixin properties not updated after modifying it.
Environment:
To Reproduce
Steps to reproduce the behavior:
Add a mixin to a test step
Change one of its properties using "Modfiy Mixin" menu item
Observe that mixin's property is not updated after modifying it.
Actual behavior When a property is changed from the MixinBuilderUI, mixin's property is not updated, See image below:
Expected behavior
Property added via a mixin must be updated after modifying the mixin.
Additional context You can access OpenTAP forum topic from here
The text was updated successfully, but these errors were encountered:
I can verify this issue and have added a fix #1373.
Sorry, something went wrong.
A fix for this is in OpenTAP version 9.23.0-beta.11+c82b3ad9 or later.
9.23.0-beta.11+c82b3ad9
I can still reproduce this with OpenTAP 9.23.1-rc.1
This is an issue with Limit mixin: https://github.com/opentap/basic-mixins/issues/2
I can confirm the fix on the Number mixin with OpenTAP 9.23.1-rc.1
Closing this
rmadsen-ks
Successfully merging a pull request may close this issue.
.Describe the bug
Mixin properties not updated after modifying it.
Environment:
To Reproduce
Steps to reproduce the behavior:
Add a mixin to a test step
Change one of its properties using "Modfiy Mixin" menu item
Observe that mixin's property is not updated after modifying it.
Actual behavior
When a property is changed from the MixinBuilderUI, mixin's property is not updated, See image below:
Expected behavior
Property added via a mixin must be updated after modifying the mixin.
Additional context
You can access OpenTAP forum topic from here
The text was updated successfully, but these errors were encountered: