-
Notifications
You must be signed in to change notification settings - Fork 51
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
Upgrade existing tests to account for the showWritableComponents flag #758
Comments
Might be some misunderstanding, tests don't relate to the helm values in the yamls at all, those are deployment side, whereas the unit tests run non-deployed code. The frontend code will never know anything about helm chart values. It's not about turning on or off tests IMO. A unit test should just exercise code based on inputs to check expected output. So simply what's needed is the test exercising the component to go "based on this value in the config store (so that's easily mockable/changeable-in-scope without needing to know anything about actual config deployment values), should this button be visible, or not?" See @jamshale comment here #743 (comment) |
Hmmm... 🤔 ... Think I get what you're saying @loneil . Just keeping in nice and simple... Or maybe I can just pass this ticket to @jamshale for a proper description. |
"Upgrade existing tests to account for the showWritableComponents flag" is perfect 😄 |
I can do this ticket. Could be reference for changing configs in the future. |
There are settings within the Tenant UI that remove various elements, depending on levels of permission. Work on #717, has turned off tests that relate to components with write permissions to the Database or Ledger.
The text was updated successfully, but these errors were encountered: