Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
This particular scenario might be unlikely to happen, but if you don't know what's causing it, how can you guarantee it couldn't happen randomly at another point? If it's a race hazard type scenario, then your intern may have just found a reliable way of reproducing a bug that only shows in 0.1% of test cases in when switching normally.
Granted, if I were management I probably wouldn't make it a priority, but I'd certainly say it should be added to the backlog and fixed when there's capacity to do so.
Do you follow test driven development?
I have mixed feeling about this test result
Well, I guess I won't be able to contribute cause tabs for life
So we're supposed to test even the most imporbable edge cases to make sure that our software is reliable. But there is a limit. We let a marketing intern go bug hunting. We use the same component in two tabs of our SPA, but we distinguish them through some parameters. The intern found that if you switch back and forth between those two tabs super fast a couple of times, the program for some reason confuses those two tabs and swaps them. Now management has listed it as a priority. When are the customers _ever_ going to do that?!
rant
test
component
edge case
tab