Confirmed users
1,504
edits
QA/Execution/Web Testing/Project for Automation: Difference between revisions
QA/Execution/Web Testing/Project for Automation (view source)
Revision as of 17:40, 25 March 2013
, 25 March 2013→Eligibility:
| Line 26: | Line 26: | ||
Let us know the scope of your project, and the timeline. The more information we have, the easier it is to work with your project. Also, the sooner you let us know a project will need Automation the better. | Let us know the scope of your project, and the timeline. The more information we have, the easier it is to work with your project. Also, the sooner you let us know a project will need Automation the better. | ||
After contacting us, we will review the project. We will incorporate all of the considerations listed above and let you know the status as soon as possible, within 3 working days. This will include whether or not the project is a good candidate for automation, and also a | After contacting us, we will review the project. We will incorporate all of the considerations listed above and let you know the status as soon as possible, within 3 working days. This will include whether or not the project is a good candidate for automation, and also a time frame that we believe it could be done in. | ||
If your project is not eligible for automation we will tell you the reasons. This information will include what might be changed in order to be eligible, if that is a possibility. | |||
==What next?== | ==What next?== | ||