Practice: safely update a scheduled login smoke test

Use a file-backed job you are allowed to edit, containing login.robot and a test tagged smoke. Download a copy, adjust one assertion to match the current login page, then replace that same remote file.

Coordinate with the owner before changing a shared scheduled job. Replace <job-id> and <project-id> with your training job and project IDs.

$ agentia testing job files list <job-id> --project <project-id>$ agentia testing job files download <job-id> --project <project-id> \  --file login.robot --output-dir ./crt-files# Edit ./crt-files/login.robot before replacing the remote file.$ agentia testing job files upload <job-id> --project <project-id> \  --replace ./crt-files/login.robot:login.robot$ agentia testing job run <job-id> --project <project-id> --include smoke$ agentia testing job schedule get <job-id> --project <project-id>

Check your results

• Check the remote file list first: --replace must target the existing login.robot, not add a second copy. Keep an untouched local backup before editing.
• The smoke run should pass with the new assertion. A failed run is a signal to review the assertion and logs, not to weaken the test.
• The schedule get result should still show the intended cron, timezone and recording policy. This exercise reads the schedule; it does not change it.