Skip to main content

Level CI troubleshooting and FAQs

On this page:

Troubleshooting

Some Repositories Are Not Visible on the Import Project Page

Issue

Certain repositories may not be visible when trying to import them into the project.

Solution

  • Ensure the application is installed on the workspace.
  • Verify that the necessary repository has been granted the required permissions.
  • If multiple repositories are not visible, double-check the repository selection settings and permissions.

Scan Fails, and Project Is Disconnected on Dashboard

Issue

Scan fails, and the project gets disconnected from the dashboard.

Solution

  • Check if there have been recent permission updates in the workspace. This can happen after new deployments.
  • Ensure that the correct application settings are still in place, and permissions have not been inadvertently modified.

Pipeline Setup – Configuration Errors

Issue

Incorrect configuration can lead to failed pipelines, wasting time and resources.

Solution

  • Before running the pipeline, double-check that the setup is correct to prevent errors and failure.
  • Test Locally: Run the following command in the terminal to test the configuration before running the pipeline:
npx level-ci --verify --configPath=path/to/level-ci.config.ts

If the terminal prints a table with scan results, then the configuration is correct, and you are good to go for the pipeline.

  • Confirm that the CI/CD config file (e.g., .yml file for GitHub Actions, GitLab, Azure Pipelines) points to the right project and branch.

Why Do My Scans Take Longer Than Expected?

Issue

Scans may run slower due to large repositories or unnecessary paths being included.

Solution

  • Use the include and exclude settings in the configuration file to scope scans to relevant code paths only.
  • Avoid scanning build artifacts (e.g., dist/, node_modules/).
  • Run a test scan locally to confirm performance.

Why Is My Pull Request Not Showing Scan Results?

Issue

PR decorations are missing, even though the scan ran successfully.

Solution

  • Ensure the GitHub App/Integration has Write access to Pull Requests.
  • Verify that the correct branch mapping exists in the project settings.
  • Check pipeline logs to confirm that the scan step completed and results were uploaded.

FAQs

Do Level CI tests run on Level servers or client servers?

Level CI supports two modes of accessibility scans:

  • With client E2E tests: Runs on client servers, using the client’s E2E framework and test cases.
  • Without E2E tests: Runs on Level CI infrastructure to detect and display accessibility issues.

Can Level CI tests run locally on client servers?

Yes. When E2E test cases and frameworks are defined, Level CI can run directly on the client’s servers.

How does Level CI handle and integrate with monorepos? Is the integration bound at the repo level or can it coordinate testing across projects?

Level CI supports monorepo setups and can coordinate testing across multiple projects within a single repository.

How are accessibility issues displayed in the repo if not tied to a PR?

Accessibility issues are displayed in the Level CI dashboard based scan scope:

  • Main branch scans: Shows all identified issues.
  • Child branch scans: Shows issues a delta relative to the main branch.
Powered by Zendesk