psh: tests improvements

[mateusz-bloch]

Description

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: (list targets here).

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing linter checks and tests passed.
• My changes generate no new compilation warnings for any of the targets.

Special treatment

• This PR needs additional PRs to work (list the PRs, preferably in merge-order).
• I will merge this PR by myself when appropriate.

[github-actions]

Unit Test Results

5 884 tests  ±0   5 241 ✔️ +8   40m 34s ⏱️ + 11m 11s
   316 suites ±0      643 💤  - 8 
       1 files   ±0          0 ❌ ±0 

Results for commit 2d6f3fc. ± Comparison against base commit 8f65cff.

♻️ This comment has been updated with latest results.

[damianloew]

Thanks or those improvements! Please be more specific in commit messages if possible.

[damianloew]

I'd suggest splitting those changes to the following commits:

• psh: cat test improvements -> psh: test-cat: add cases with writing a content

• psh: add cleanup in tests

• psh: enable back test-touch

• psh: small improvements and cleanup in tests

IMHO it will be much more readable in commit messages what have been changed.

[damianloew]

I'd suggest splitting those changes to the following commits:

• psh: cat test improvements -> psh: test-cat: add cases with writing a content
• psh: add cleanup in tests
• psh: enable back test-touch
• psh: small improvements and cleanup in tests

IMHO it will be much more readable in commit messages what have been changed.

Of course you can change the messages a little bit if you want

[damianloew]

LGTM