Investigate the parts of e2e test that takes most of execution time. That's profile the e2e test execution time to get parts that are taking the most time which could be cached. A proxy cache could be used to cache parts of the test run that take most time  i.e. installing dependencies. However we’ll have to profile which parts of the existing tests are taking the most time. For example , if the dependencies installation operation (node-modules) is cached, every PR would use the cache except a new dependency is required. If a new dependency is required it would be added to the cache, and will be immediately available for use by the PR. The release team would be able to help us with the cache deployment. 

AC:

Identify the part(s) of the e2e tests that is taking the most of the execution time which could be cached

Open question:

Is there any tool that we can use  to profile test job in Prow CI?{}