Hi Chris,
Looks like a great service. It definitely sounds like we can use this for the 1.3 and 1.4 branches to prevent breakage.
To those who don't know about the scope of our testing, you told me that these are the types of tests that we have currently in place:
- number formatting
- number parsing
- template handling
- basic form and request api
- api tests that run against the db (but never commit)
- pod
- pod coverage
Would be good to assure that our release branches remain stable and don't fail tests when we commit/merge changes. I think this would be a good next step in our QA.
Regards,
Erik.