Do you have a standard pricing structure for building an eValid test? What are the limits on size and complexity?Yes, in addition to providing licenses to the eValid product so you can build your own tests, we also provide services that generate tests according to you own specification.
We have (as you might expect) a great deal of experience in building functional tests using eValid, and we generally are able to deliver test scripts to you that are 100% self-synchronizing and also 100% load-test safe.
Self-synchronizing means that you can make any adjustment to the Wait Time Multiplier you like -- including eliminating all delays, a Wait Time Multiplier of zero -- and the test will still run successfully. This is done with eValid structural commands and with eValid DOM-synchronization commands.
Load-test safe means that the tests can be run in multiple eValid instances on the same machine, without interfering with each other. That way, such a test can run 100's of browser users on one regular machine -- and 1,000's of browser users on a beefy, multi-user computer (like the ones we deploy when doing cloud-based loading work for customers).
We are so confident that we can complete such test script development projects on a tight budget -- and who isn't interested in having tight control of costs these days? -- that we offer such test creation mini-projects for a typical fixed-price fee $1,495 per script. And we take all of the engineering risks if it takes us longer than our nominal time budget. We have a 100% deliver success ratio on such mini-projects.
There are size constraints and limits of course, but for this very modest price we generally deliver a test script that has all of the above properties but in addition typically has coverage for up to 200 test steps (test plan imperatives like "click this..." or "select that..."), and can play back as long as about 5 minutes with no wait times.
You might think that 5 minutes is not a long time nor a very comlicated script, but when eValid scripts run with zero delay times, we find that the resulting test script, which may be upwards of 400 lines or more, will cover a very great deal of "functional ground."
All we need to get going on a mini-project like this is a step-by-step outline of your test, and appropriate access credentials for your application. If you don't want to write your test plan down, we can even include doing that step with a phone interview.