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.

Required fields*

Rev

6

I think this is a great way: Show the team first how end-to-end tests can be automated and run on every build. They don't even need to write the tests, you can do that all by yourself if the team is hard to convince. As soon as they see how great is to have automated feedback each time they change something, they will be the ones asking you how to do more of that stuff.

Sergio Acosta
– Sergio Acosta

2010-10-11 04:31:37 +00:00
Commented Oct 11, 2010 at 4:31
1

You second para is spot on. The code is hard to test but because its on a legacy code-base with no tests, refactor is not an option. The test then can be so difficult to implement that it turns off people to even bother.

Todd
– Todd

2018-07-30 14:07:31 +00:00
Commented Jul 30, 2018 at 14:07

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 »