Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

This argument only applies from a position where all necessary tests have already been written. It does not account for a scenario whereby a developer discovers that a test that should've been written long ago was never added to the test suite. While not wrong, per se, it is idealistic as a baseline for judging whether a test should be written today or not.

Flater
– Flater

2024-07-23 07:14:28 +00:00
Commented Jul 23, 2024 at 7:14
@Flater I explicitly covered that scenario

jwenting
– jwenting

2024-07-23 07:51:02 +00:00
Commented Jul 23, 2024 at 7:51
It is possible for OP's current task to be listed as a bugfix. The distinction between a bugfix and a change (i.e. whether the current behavior was once intended (change) or not (bugfix)) has no bearing on whether it should be backed by a test. Bugfixes also tend to need new tests, as the existence of the bug indicates that the test suite failed to cover this gap in the first place (else it wouldn't have been released with the bug). You've already made the mistake (bug) once, so refusing to write a test effectively opens you up to regressions on a mistake you've already made before.

Flater
– Flater

2024-07-23 23:06:35 +00:00
Commented Jul 23, 2024 at 23:06

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »