Jobs

A job in Bytesalt represents a single test run. When you execute the bytesalt start command, you are creating a new job. Each job is assigned a unique ID that you can use to track its progress.

Job Lifecycle

A job goes through several stages from creation to completion. The typical lifecycle of a job is as follows:

• Queued: When you first create a job, it is placed in a queue. It will remain in this state until a testing agent is available to process it.
• Running: Once an agent picks up the job, its status changes to “running.” At this stage, the AI agent is actively testing your application based on the provided context.
• Succeeded: If the test run finishes without any critical errors, the job is marked as “completed.” You can then view the detailed report in your Bytesalt dashboard.
• Failed: If the job encounters a critical error that prevents it from continuing, its status will be set to “failed.” This could be due to issues with the testing environment or problems with the application under test.