The problems caused by 1.2.6 got me thinking. I read somewhere that
Chrome was permanently running a suite of tests that involved it
crawling web sites. I was wondering what regression testing was done
for GAE (and concluded not very much).
How about this as a win-win for Google and developers...
GAE apps optionally include a Junit test suite. This test suite could
be defined in appengine-web.xml using an ant-like syntax, eg
<junit fork="no" haltonfailure="yes">
<test name="couk.cleverthinking.cc.junit.StringsTest" />
<formatter type="plain" usefile="false" />
<classpath refid="test.classpath" />
</junit>
Whenever the Junit suite is run, GAE automatically appends a testing
qualifier to the Kind, (eg. Dept and Emp become DeptTesting and
EmpTesting). A bit of quota magic would also be needed.
Now developers can easily run test suites to spot problems in their
code that might otherwise be difficult to spot.
More importantly, Google can run all of these test suites to
regression test new releases. Failure reports can optionally be sent
to the app owner, eg. to implement API changes ahead of time.
implements a mechanism where apps can include their Junit test suite.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
