Skip to content

Conversation

3v1n0
Copy link
Collaborator

@3v1n0 3v1n0 commented Jun 13, 2025

Add more tests for the authd default state that we were not checking in any integration test before

UDENG-3646

@3v1n0 3v1n0 requested a review from a team as a code owner June 13, 2025 12:29
@3v1n0 3v1n0 force-pushed the tests-brokerless-login branch from 3506670 to 8dbf2a0 Compare June 13, 2025 17:03
3v1n0 added 3 commits June 16, 2025 16:49
Do not show the sshd messages unless we have a failure, this avoids
spamming CI, but also it seems that in such context they get scrambled.

At the same time they're useful during debugging, so don't change the
behavior when we're in an interactive terminal
…orks

It's kind implicit in the previous tests, but still let's test the non
interactive behavior too
3v1n0 added 6 commits June 16, 2025 20:45
Otherwise mkhomedir may fail in trying to create it, and so SSH:
  Could not chdir to home directory /home/user-integration-cached:
  No such file or directory
In case the user is considered already existent:
 - Create the directory when parsing the DB
 - Ensure the directory already exists at test time

Otherwise:
 - Ensure no user home directory exists before user has been created
 - Ensure the user home exists after user logged in
In case the local broker is used, it should never be auto-selected for
non-local users, so do this in test
Allow to run authd without any broker, and just run the tests to ensure
that we don't break this basic experience for various setups and
special cases
Avoid printing unneeded private values while print the internal data,
using JSON to help us doing that easily.
If safeMessageDebug is used to print multiple types, only the first one
is safely parsed, while the others are not.

This won't cover (and it's not even possible) to do it in case a format
is used, but should allow to easily and safely print things around anyways
@3v1n0 3v1n0 force-pushed the tests-brokerless-login branch from 70518a6 to f8aa703 Compare June 16, 2025 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants