Meta: Skipped (unit) tests for multiple reasons

[Devansh-46]

Skipped Tests

This document lists tests that are currently skipped and the reasons for their skipping. The aim is to address and resolve these issues to ensure all tests run as expected.

SSH related

common/test/test_restore.py

• TestRestore.test_localSSH: Skipped if no local SSH server is available.

common/test/test_snapshots.py

• TestSnapshots.test_localSSH: Skipped if no local SSH server is available.

common/test/test_sshtools.py

• TestSSHTools.test_sshCommandAvailable: Skipped if the ssh-keygen command is not available.
• TestSSHTools.test_localSSH: Skipped if no local SSH server is available.

common/test/test_takeSnapshot.py

• TestTakeSnapshot.test_localSSH: Skipped if no local SSH server is available.

Related to linting

common/test/test_lint.py

• TestLint.test_pylintAvailability: Skipped unless on Travis CI or PyLint is available.

qt/test/test_lint.py

• TestLint.test_onTravisOrPylintAvailable: Skipped unless on Travis CI or PyLint is available.

Others

common/test/test_snapshots.py

• TestSnapshots.test_isRoot: Skipped if running as root.
• TestSnapshots.test_noGroups: Skipped if the user is in no other group.

common/test/test_backintime.py

• TestBackInTime.test_quietMode: Skipped because "--quiet is broken due to some non-filtered logger output."

[buhtz]

Hello Devansh, Thank you for taking the time to report. I appreciate your feedback

I see no real problem. Can give more details about your concerns and maybe suggest solutions? Do you plan to work on it and provide an PullRequest?

• test_lint.py: Linting is not a real unit test. There is no need to make this run on every machine except the developers one.
• SSH related skippings: This might not be the best solution. But it is for contributors on beginner level. No need to fail if they where not able or forgot to setup SSH. The same goes for ssh-keygen.
• is_root and noGroups: Makes not much sense to me, too. Need to investigate that tests to decide about it. Tests shouldn't be run as root of course.

What could be discussed is to force the SSH tests on TravisCI. We do this for the linter tests, too. They have to run on TravisCI and fail if the setup is not OK.

Best regards,

[buhtz]

The names of files, classes and methods you provided are not valid. Some of them do not exist. Please modify your initial post.

This smells like AI content. Also your profile smells like AI. Please provide a valid answer asap. I still reported your profile to Microsoft so they can have a look.