You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we have only one test: it's calling the rules with standard arguments and checks if all packages were installed correctly.
But as we grow, new arguments are added to the rules and possible input configurations are multiplying. We want to test if execution is successful depending on different inputs to the rules, not only with one standard input.
As these are repository rules, they are used inside a WORKSPACE file. This means that each different input configuration requires a different workspace.
It would be best to just have some configuration matrix with different input values. The test framework would make a workspace for each combination of values, check the execution there, and report which ones fail. The test can be the same as it is now - checking if installed package versions are correct.
The text was updated successfully, but these errors were encountered:
Now we have only one test: it's calling the rules with standard arguments and checks if all packages were installed correctly.
But as we grow, new arguments are added to the rules and possible input configurations are multiplying. We want to test if execution is successful depending on different inputs to the rules, not only with one standard input.
As these are repository rules, they are used inside a
WORKSPACE
file. This means that each different input configuration requires a different workspace.It would be best to just have some configuration matrix with different input values. The test framework would make a workspace for each combination of values, check the execution there, and report which ones fail. The test can be the same as it is now - checking if installed package versions are correct.
The text was updated successfully, but these errors were encountered: