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
Performance testing or measure often requires real data. And we have that in our own repo. So it's tempting to use our production code base as test bed for our performance testing.
From a Configuration Management perspective this is wrong. Despite the fact that it may sometimes require an effort to setup an different environment to use as test bed. It's not optional.
Tests should have zero impact on the code base, issue, project info, or even workflow runs - Setup a real testbed and work there. 🙏
Work on other branches (and don't merge them back to main), setup branch specific workflows (and throw them away when you are done)
Or even better, setup a separate repos and use that as a testbed - all together.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Here's and example:
Performance testing or measure often requires real data. And we have that in our own repo. So it's tempting to use our production code base as test bed for our performance testing.
From a Configuration Management perspective this is wrong. Despite the fact that it may sometimes require an effort to setup an different environment to use as test bed. It's not optional.
Tests should have zero impact on the code base, issue, project info, or even workflow runs - Setup a real testbed and work there. 🙏
Work on other branches (and don't merge them back to main), setup branch specific workflows (and throw them away when you are done)
Or even better, setup a separate repos and use that as a testbed - all together.
Beta Was this translation helpful? Give feedback.
All reactions