View source | View content page | Page history | Printable version   

Projects:Static Resources Caching/QA


Automatic Tests

This project affects to the whole application and in particular to the log-in process, taking into account that new cache mechanism must allow the correct loading of the static resources. The smoke tests currently covering those processes should be enough to ensure that the normal flows continue working fine.

Manual Tests

Some additional manual tests have been performed in order to ensure that some basic features affected by this project are still working fine:


This project aims to improve performance and the scalability in terms of number of requests and time required to compute and deliver the static resources.

The following sheet shows, among others, the requests and time spent to process the static resources before the changes introduced as part of this project.

They can be compared with the improvements achieved:

Number of Requests

Regarding javascript content generated with the StaticResourceComponent, after the first successful login 0 requests are done, this is because:

The following screenshot shows the javascript requests fired once the javascript static resources information is in cache.


Regarding the css content generated with the StyleSheetResourceComponent, after the first successful login 1 request is done, but it takes the information from cache, thanks to the ETag.


Component Generation Time

It is also has been measured how long takes the components to generate the content when the new cache mechanism is used.

The results of this measurement are summarized in the following sheet.

The StaticResourceComponent (javascript) and the StyleSheetResourceComponent (css) are respectively 97% and 96% faster when using the cache.

Code Review

Retrieved from ""

This page has been accessed 696 times. This page was last modified on 28 April 2017, at 13:00. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.