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.

All of our integration tests put together run for about 9 minutes in total. Only a few at a time will fail so lets say depending on which ones it's at most a minute of waiting time to retreive the debugging logs you need. We can enable or disable debugging logs easily and we have a stacktrace so we can kind of judge where the error is coming from without the debug logs. To me the point to keep the debugging-leve for our testing logs was nonsensical.

Byebye
– Byebye

2019-09-27 21:44:53 +00:00
Commented Sep 27, 2019 at 21:44
I've marked this as the answer due to your indication of the tests being broken if you need debug logs for successful tests.

Byebye
– Byebye

2019-09-27 21:50:00 +00:00
Commented Sep 27, 2019 at 21:50

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 »