HTML Testrunner is stuck in middle. No report No error

Is there any way to get the report after each use case and not after complete test case ??
I am facing the issue of my test case being stuck midway.

since its stuck, My test case wont continue and if i force exit, I dnt get any report

The standard approach with test running:
- create a suite containing the tests you want to run
- setup a testrunner (HTMLTestRunner in this case defining the reportfile)
- testrunner.run(suite)
- close report file in case one was created

If you follow this concept, then you may setup as many test steps as you want, by simply setting up a suite (might only contain one test) and run it with a specific report file.

About how to select tests as members of a suite you have to consult the Python unittest docs.

Hi RaiMan, Thanks for your reply but I am using the standard approach only.

I have been running my main file for the past 5 months and also i integrate new use case time to time to the existing main file. Now from a couple of days I am unable to get any report. The instance is stuck at random places.

I separated it out to check if there is any error in coding but it ran successfully.

I would say upto 20 use case or so, I had no issue. I get my report (both success and failure )Now after adding three use case my complete main file hangs at random places. Is there any chance of memory leaks?

ok, then you seem to know what you are doing ;-)

What version of Sikuli are you using?

Are you using the modified runner (takes screenshots on failures)?

Since the problem happened after you added the tests: Is the original version (without the new tests) still working?
If yes, are there any new features you are using, that you never used before in the other tests?

Do all tests need to be in one script? (the script might be too big - there is a restriction of 64KB from Java/Jython)? Why not divide it into modules, that are imported and run by a main file (which adds some options for more flexibility)

MemoryLeaks: different versions of Sikuli had different cases of memory leaks.
These should be fixed with 1.0.1+

But I have to admit, that from time to time someone complains about random crashes/hangs of long running scripts. But till now, these cases where rather seldom and finally accepted as risk but without any solution.

So the only way to get a result is, to go back to a running situation and add new things step by step until it does not work anymore.

What I do not understand: If you are producing different report files for different test suits in your run: How can it be that you do not get any reporting?