Consider implementing end-to-end testing on the real file system #2580
Labels
Epic
Groups multiple user stories. Can be grouped under a theme.
need-investigation
The issue needs the second look and more investigation
triaged
The issue was evaluated by the triage team, placed on correct area, next action defined.
The current end-to-end tests use an in-memory file system. Hence, some of the features were left untested, such as the run script post-action and the chmod post-action: seems like the corresponding tests could not be written within the current testing infrastructure. We already run into the issue with the absence of these tests: the change in one of our dependencies broke the chmod post-action and that was not noticed that for a long time (PR #1555, PR #2579, issue #1547).
Consider designing and implementing proper end-to-end testing on the real file system for these post-actions.
The second option here is to find a workaround / somehow to leverage the current infrastructure and write proper tests for these post-actions if it is decided not to make end-to-end testing on the real file system.
The text was updated successfully, but these errors were encountered: