I have created a rather complex tool for fixtures generation for my app and thought about adapting it for testing purposes, which could potentially work as acceptance and both load testing.
For that, on the contrary of using
meteor test (which still could be used for unit testing) I thought about creating a separate application that would consists specifically from instructions for nightmare to go to the app and in a virtual browser check/interact with specific dom elements, enter the fixtures data (that is generated reusing the code for fixtures generators), and thus ‘emulate’ behaviour of actual users.
Before I start doing this, asking for some help from community:
Is it worth doing this in general? I assume I won’t be able to do this on a CI server, right? Meaning this approach won’t allow me to actually test the app before pushing new code to master/live, right?
Could this approach help to perform a load testing? I could theoretically program several servers to create thousands of real users-like calls to a pre-production app on galaxy and see how well it will perform, to estimate how many and which servers I might need under which load.
Have you done something like this or maybe I should consider anything different?