Ensure performance of your software in-browser using automated web performance testing. Our vision for Web Performance testing is to provide actionable performance data for most developers against top browsers in 5 minutes or less.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
This page is maintained by the Product Manager for Testing, James Heimbuck (E-mail)
Up next for Web Performance is gitlab#10585 so developers can quickly understand any browser performance degredation from changes they have introduced without having to run a scan of the entire site.
This category is currently at the "Minimal" maturity level, and our next maturity target is "Viable" (see our definitions of maturity levels). Key deliverables to acheive this are:
While, just as one could orchestrate any number of web browser testing tools with GitLab CI today, Jenkins, Travis or CircleCI could be used to orchestrate web browser testing tools in similar ways. None of these offer an out of the box web performance option but there are integrations available for them for top tools such as Google's Lighthouse and sitespeed.io.
In order to remain ahead of the competition we should continue to make GitLab a rich interface for Web Performance testing data for all contributors and expand beyond the current focus on the developer needs in a merge request. The Vision Items for the category reflect this direction.
The most popular issue to date is gitlab#9878. We are actively seeking additional input from customers on how they are using the web performance data already available today before tackling this issue.
When we think out further about Web Performance there are opportunities to solve problems for customers like needing to track web performance over time or finding performance issues sooner by automatically running Browser Performance testing on changed pages.