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
In our unit tests, we currently do not mock GitHub input consistently, even when it is not within the scope of the specific test being conducted. This leads to unnecessary dependencies on GitHub input, which can complicate testing and potentially introduce issues unrelated to the actual code under test. For example, in the project name resolver test, the GitHub input is not part of the logic being tested but is still present, which could lead to false failures or distractions during testing.
Wanted
We need to mock every instance of GitHub input in our unit tests where it is not relevant to the scope of the test. By doing this, we can reduce unnecessary dependencies and ensure that our unit tests focus solely on the logic under test. This will improve test reliability, make the tests easier to maintain, and ensure they are faster and less prone to failure due to unrelated input.
Note
This might automatically resolve the flaky GitHub Actions Pipeline runs
The text was updated successfully, but these errors were encountered:
Situation
In our unit tests, we currently do not mock GitHub input consistently, even when it is not within the scope of the specific test being conducted. This leads to unnecessary dependencies on GitHub input, which can complicate testing and potentially introduce issues unrelated to the actual code under test. For example, in the project name resolver test, the GitHub input is not part of the logic being tested but is still present, which could lead to false failures or distractions during testing.
Wanted
We need to mock every instance of GitHub input in our unit tests where it is not relevant to the scope of the test. By doing this, we can reduce unnecessary dependencies and ensure that our unit tests focus solely on the logic under test. This will improve test reliability, make the tests easier to maintain, and ensure they are faster and less prone to failure due to unrelated input.
Note
This might automatically resolve the flaky GitHub Actions Pipeline runs
The text was updated successfully, but these errors were encountered: