I was thinking here, a browser for education purposes, slow, insecure, requiring a lot of memory but very useful to understand all the cycle of HTTP and also used as probe test to check 'what is real used and who owns the skin'. The recipe is pretty simple...
1 -> A HTTP Browser
2 -> A JScript Engine
3 -> A Database
4 -> A JVM
5 -> Out of a 'development platform' which means no 'free lunch for heroes or tchecs'.
Other tools of your choice. All running in Java with open source tools, to understand all development life cycle since the browser to the application it self. Very complex, slow, requiring a lot of memory, but using open standards so, easy to understand, code best practices, and what? The best of all worlds. Which means 'no SO dependent native code' to require certification on a specific platform.
THe main advantage of such tool for example is differently from tools that runs on a specific browser like Selenium can be used as test on specific user agents, for backward forward compatibility, it is not a bot since requires user interaction (the developer remains working as a tester), indeed probably Selenium is being used all around WEB, mimicking user behavior. All the gestures that are human dependent are recorded like mouse moves, link clicks, that can be used for some sort of 'statistical analysis' for behavior in front of computer.
Also can reduces cost for development-test team, obligating team to continuing studying, until the end of their miserable life, "SLAVE" jump.
