Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

shellrecorder: fail if writing outside of /tests #1887

Closed
2 tasks
Tracked by #4482
markus2330 opened this issue Apr 4, 2018 · 7 comments
Closed
2 tasks
Tracked by #4482

shellrecorder: fail if writing outside of /tests #1887

markus2330 opened this issue Apr 4, 2018 · 7 comments
Labels
enhancement stale testing errors in tests without implication on real usage

Comments

@markus2330
Copy link
Contributor

markus2330 commented Apr 4, 2018

Although TESTING.md clearly defines that only /tests/<testname> is allowed for writing, quite some tutorials, plugins, tests do differently. Following Elektra paths seem to be used:

@markus2330
Copy link
Contributor Author

As discussed, only /tests is allowed.

@sanssecours sanssecours mentioned this issue May 14, 2018
7 tasks
sanssecours added a commit to sanssecours/elektra that referenced this issue May 14, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 14, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 17, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 17, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 18, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 18, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 19, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 19, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 19, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 19, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 20, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 20, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 21, 2018
While this update will **not** catch every occurrence of test code that
saves data outside of `/tests`, it should handle most cases without
adding to much overhead.

This commit addresses issue ElektraInitiative#1887.
sanssecours added a commit to sanssecours/elektra that referenced this issue May 23, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 23, 2018
While this update will **not** catch every occurrence of test code that
saves data outside of `/tests`, it should handle most cases without
adding to much overhead.

This commit addresses issue ElektraInitiative#1887.
sanssecours added a commit to sanssecours/elektra that referenced this issue May 23, 2018
sanssecours added a commit to sanssecours/elektra that referenced this issue May 23, 2018
While this update will **not** catch every occurrence of test code that
saves data outside of `/tests`, it should handle most cases without
adding to much overhead.

This commit addresses issue ElektraInitiative#1887.
@markus2330
Copy link
Contributor Author

The next step would be to let the shell recorder fail if data outside of /tests is accessed.

@markus2330 markus2330 changed the title Unify which Elektra paths are used for tutorials tests shellrecorder: fail if writing outside of /tests Feb 17, 2019
@markus2330 markus2330 added the testing errors in tests without implication on real usage label Apr 12, 2020
@stale
Copy link

stale bot commented Apr 15, 2021

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@stale stale bot added the stale label Apr 15, 2021
@stale
Copy link

stale bot commented Apr 30, 2021

I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@stale
Copy link

stale bot commented May 2, 2022

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@stale stale bot added the stale label May 2, 2022
@markus2330 markus2330 removed the stale label May 3, 2022
@markus2330 markus2330 removed this from the 0.9.* milestone Nov 18, 2022
Copy link

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot added the stale label Feb 19, 2024
Copy link

github-actions bot commented Mar 4, 2024

I closed this now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 4, 2024
@github-project-automation github-project-automation bot moved this to Done in 1.0 Aug 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement stale testing errors in tests without implication on real usage
Projects
Status: Done
Development

No branches or pull requests

2 participants