Timeline for Should we do peer reviewing with end-to-end tests?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 8:38 | comment | added | 501NotImplemented | In other words, the inability to review the changes within the files might be a serious point to consider migration from existing toolset into alternative. But that fact needs to be carefully evaluated. | |
| Jun 15, 2020 at 8:35 | comment | added | 501NotImplemented | Don't let the tools to drive the process, adjust the tools according to the process. I perform (or performed) code review using the web-based platforms like GitLab/BitBucket/Azure DevOps. The changes are listed within the merge request. For the files itself - there might be an issue since the changes might not be listed correctly. Unfortunately, I don't have an easy solution for that. That's the downside of using the tools that don't allow us to review the changes easily. | |
| Jun 15, 2020 at 8:11 | comment | added | Ice-Blaze |
Had you to tackle tools files extension that are not pure code? In my case we use ReadyAPI and JMeter and both use xml files which are hard to compared with a diff. I feel bad to change the workflow of the company because I have the feeling I had to change all the tools. But if you had the issue I would be curious how you handle to switch from tools which are not very compliant with versioning tools.
|
|
| Jun 15, 2020 at 8:02 | history | answered | 501NotImplemented | CC BY-SA 4.0 |