Test with GitLab CI/CD and generate reports in merge requests
Use GitLab CI/CD to test the changes included in a feature branch. You can also display reports or link to important information directly from merge requests.
| Feature | Description |
|---|---|
| Accessibility Testing | Automatically report A11y violations for changed pages in merge requests. |
| Browser Performance Testing | Quickly determine the browser performance impact of pending code changes. |
| Load Performance Testing | Quickly determine the server performance impact of pending code changes. |
| Code Coverage | See code coverage results in the MR, project or group. |
| Code Quality | Analyze your source code quality using the Code Climate analyzer and show the Code Climate report right in the merge request widget area. |
| Display arbitrary job artifacts | Configure CI pipelines with the artifacts:expose_as parameter to directly link to selected artifacts in merge requests. |
| Unit test reports | Configure your CI jobs to use Unit test reports, and let GitLab display a report on the merge request so that it’s easier and faster to identify the failure without having to check the entire job log. |
| License Scanning | Manage the licenses of your dependencies. |
| Metrics Reports | Display the Metrics Report on the merge request so that it’s fast and easier to identify changes to important metrics. |
| Test Coverage visualization | See test coverage results for merge requests, in the file diff. |
| Fail fast testing | Run a subset of your RSpec test suite, so failed tests stop the pipeline before the full suite of tests run, saving resources. |
Security Reports
In addition to the reports listed above, GitLab can do many types of Security reports, generated by scanning and reporting any vulnerabilities found in your project:
| Feature | Description |
|---|---|
| Container Scanning | Analyze your Docker images for known vulnerabilities. |
| Dynamic Application Security Testing (DAST) | Analyze your running web applications for known vulnerabilities. |
| Dependency Scanning | Analyze your dependencies for known vulnerabilities. |
| Static Application Security Testing (SAST) | Analyze your source code for known vulnerabilities. |