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.

2

Thank you for the detailed answer. I like the idea that E2E Tests should work with artefacts and not branches. The things you describe make perfekt sense. However, they are also a lot of work to set up and maintain. Our team has only a few developers so I wonder if there is a more pragmatic approach that gets us ~80% of the benefits for only ~20% of the work.

Johannes Stricker
– Johannes Stricker

2021-09-14 12:45:59 +00:00
Commented Sep 14, 2021 at 12:45

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 »