Confirmed users
753
edits
| Line 5: | Line 5: | ||
=Goal= | =Goal= | ||
Both the A*Team and Automation Services have a requirement to create a UI functional testing framework that allows testing of both the browser chrome and the the browser content. The approach that we want to take is to have a server client architecture that allows us to scale our tests and parallelise our tests. This will maximise our tests test execution in the smallest time frame. | Both the A*Team and Automation Services have a requirement to create a UI functional testing framework that allows testing of both the browser chrome and the the browser content. The approach that we want to take is to have a server client architecture that allows us to scale our tests and parallelise our tests. This will maximise our tests test execution in the smallest time frame. | ||
This would then translate commands to hook into the browser. Approach being investigated for proxy to browser communication can be found [[Auto-tools/Projects/JSON_Protocol_Testing|here]]. The approach, at time of writing this, that appears to be the the best is a hybrid of 2 and 3 | |||
==Option 1== | ==Option 1== | ||
| Line 10: | Line 12: | ||
Server Architecture The server is going to be a Jetty Server on the device with servlets to handle the different commands available in the JSON Wire Protocol. This approach also means that we can use the Selenium Grid to parallelise since devices can be added and the central hub would understand and forward the commands to this server. | Server Architecture The server is going to be a Jetty Server on the device with servlets to handle the different commands available in the JSON Wire Protocol. This approach also means that we can use the Selenium Grid to parallelise since devices can be added and the central hub would understand and forward the commands to this server. | ||
[[File:option1.png]] | [[File:option1.png]] | ||