Context Navigation

Changes between Initial Version and Version 1 of Ticket #61154, comment 23

initial	v1
58	58	You can't say this! You are in the Test Team bruh!!!. This is why first we need to spot the code that already conflicting live, and then we should code to fix it, not the other way around (unless we are developing a new feat). I read this somewhere recently, but refactoring is very rare in WP unless there is a really good reason behind to prove everything.
59	59
60		Not abiding to this "rule" forces spending unnecessary time resources from many, not only the coder's time but others' time because rarely anyone will really want to step forward for something like this (unless you plan to commit by yourself and have someone that peer reviews it loosely, that also happens a lot, ngl).
	60	Not abiding to this "non-written-rule" forces spending unnecessary time resources from many, not only the coder's time but others' time because rarely anyone will really want to step forward for something like this (unless you plan to commit by yourself and have someone that peer reviews it loosely, that also happens a lot, ngl).
61	61
62	62	I'm providing this test report as an example of what could be done preventively, imagine that its kind of exhausting if it should be done in each single ticket. I've made it just because I'm collecting a set of proofs (like this) to demonstrate that this behavior of coding before tests is problematic and leads to what I call `needs-testing-workflow-waste` (and the main root cause of +10-year-old tickets, dozens stuck in this situation)