I wrote a new test automation application because in my primary personal application I need to run test automation in the browser, I needed it to be faster than prior existing solutions, and I needed it to be distributed to browsers on different machines of the same local network. The test samples for this new test automation application are just JSON data structures defined against a TypeScript interface, so the code editor literally tells you what properties are missing to complete a test and what the allowed values are.
Its faster than other test automation tools for the browser because it does not make use of CDP. Instead a test receiver is required to be embedded in the given page(s) which evaluates the tests and transmits the results. Its also faster because it only uses WebSockets and not HTTP. I was executing 89 tests comprising a total of 284 points of evaluation against event execution in the browser at 6.22 seconds from Node start to test completion.
This took tremendous trial and error to get correct, but now I have experience writing and executing test automation at a depth that almost nobody else has and can do it faster than all the popular test automation applications. It also required that I rewrite large portions of my primary personal application to make everything WebSocket based for faster execution across the board and also to greatly simplify the service/transmission architecture on both the browser and the Node layer.
This experience is winning me employment at higher rates when many senior developers are challenged to find new employment. Writing this new test automation did not scale at all and took tremendous time to get correct and stable, but now it allows scale and rapid execution of colossal refactors I could never do before. Since the test automation executes on the local machine only in less than 10 seconds I find that I was running it dozens of times a day for large feature enhancements.
I wrote a new test automation application because in my primary personal application I need to run test automation in the browser, I needed it to be faster than prior existing solutions, and I needed it to be distributed to browsers on different machines of the same local network. The test samples for this new test automation application are just JSON data structures defined against a TypeScript interface, so the code editor literally tells you what properties are missing to complete a test and what the allowed values are.
Its faster than other test automation tools for the browser because it does not make use of CDP. Instead a test receiver is required to be embedded in the given page(s) which evaluates the tests and transmits the results. Its also faster because it only uses WebSockets and not HTTP. I was executing 89 tests comprising a total of 284 points of evaluation against event execution in the browser at 6.22 seconds from Node start to test completion.
This took tremendous trial and error to get correct, but now I have experience writing and executing test automation at a depth that almost nobody else has and can do it faster than all the popular test automation applications. It also required that I rewrite large portions of my primary personal application to make everything WebSocket based for faster execution across the board and also to greatly simplify the service/transmission architecture on both the browser and the Node layer.
This experience is winning me employment at higher rates when many senior developers are challenged to find new employment. Writing this new test automation did not scale at all and took tremendous time to get correct and stable, but now it allows scale and rapid execution of colossal refactors I could never do before. Since the test automation executes on the local machine only in less than 10 seconds I find that I was running it dozens of times a day for large feature enhancements.