|
FeatureCandidates
These are some of the ideas for the next release of GAEUnit. Please feel free to comment and suggest new features. Support for Coverage: GAEUnit does not provide support for coverage testing. We could provide support for determining coverage and generating an html report. We will not supply the coverage module with our source and it will be the choice of the users if they want to run GAEUnit with coverage.(coverage can be easily installed from pypi). A New Interface: The present gaeunit users presently specify the tests to run as URL arguments. Instead, we can have a starting page or a welcome page where users can mention the tests to run. The tests to run can be collected in a text box and whether to run all the tests through a radio button. We can also have options for users to choose if they want to see only the summary of the results such as only the tests which failed. There can also be an option to hide the traceback when the tests are run and just display a clickable line which shows the test which had failed. After the completion of the tests, the user can click on the line and it will expand to display the traceback corresponding to the failed test. |
► Sign in to add a comment
How about being able to set the logged in user?
I would like to include functionality to run test only after successful logging as admin. This is useful if you want to run a test in GAE production environment.
The login should not be presented if running in the SDK server.
I second running Django tests. I'd love to see a more informative runner UI, which first returned the tests and displayed them in a list or something and then started running them one at a time from the browser.
As a matter of fact, I am currently working on improving the UI. The first change I am working on is to run the tests one at a time while showing incremental progress. Then, I hope to be able to display a list of available tests from which to choose.
Displaying the list of tests that ran would be useful as well.
Being able to invoke the django test client seems pretty useful. Right now I get: Environment variable DJANGO_SETTINGS_MODULE is undefined. when trying to use it.
I've got the test client working actually, by getting GAEUnit to InstallAppengineHelperForDjango?() from the Django Helper =)
Django support is under developing. And the first version should be available in few weeks.
My implementation is based on App-Engine-Patch, but it should be OK for all Django implementations.
can we also include coverage.py for code coverage?
+1 doctest and coverage.py
By the way, great work George and Steven! GAEUnit is still one of the easiest ways to get unit tests up and running in Python apps.
Running tests from the command line is crucial to me.
+1 coverage.py
Great work George and Steven. I dropped GAEUnit into my appengine project and was adding and running tests in less than 10 minutes.
Yes, coverage.py definitely +1.
Just 3 words for you !
Cov er edge
PLEASE!
Ok maybe that's just one real word.
Hey, thanks... GAEUnit is working great for me. I would also like to be able to set the logged in user. Maybe it is already possible, but I haven't found it in my searching.
@tim Take a look at http://blog.sudhirj.com/2008/11/testing-app-engine-authentication-with.html
You can set GAE UNIT to only run as an admin with the following in your app.yaml:
- url: /test.
The above will require you to log in as admin to run the test harness.
+1 coverage.py
what about running named lists of tests?
I am not sure GAEUnit does it, so I prefer asking :-) Would it be possible to include the class & method names within the tests execution report? And A status and the execution time?
How about systematically logging success & failures in a file?
+1 for running tests from the command line.