So far we have looked at how to use WebPageTest to configure and analyze synthetic web performance tests. We started by learning what the test results mean and how to read a waterfall. In Part II, we learned how to fine-tune the test configuration to more accurately reflect real-use cases and how to simulate anomalies like third-party outages. Until now, everything has gone through the public WebPageTest UI.
Part III is all about advanced use cases of WebPageTest. The users who will benefit the most from this unit are enterprise-level developers who have very high demand for test automation and monitoring, especially for prerelease web applications. In the following chapters, we will look at the application programming interface (API) of WebPageTest and use it to run tests and get test results. We will also cover the process of getting a local version of WebPageTest to run privately on our own machine. Using these concepts, you will be able to leverage the versatility of WebPageTest for even the most demanding requirements for synthetic testing.