[
http://mifosforge.jira.com/browse/MIFOS-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafal Lewandowski updated MIFOS-3594:
-------------------------------------
Description:
Specific test cases' descriptions will be added later.
[02.09.10] Test cases to be added:
- test case showing that if any batch job runs have been ommited (e.g. because
the application was shut down), the batch system will calculate the dates of
missing runs and execute them
- test case showing that if previous runs of a job have failed, the batch
system will re-run them one after another, starting with the oldest one (one
that failed first)
- test case showing that if a problem occured during re-running one of the
failed jobs, all re-runs that executed successfully will be marked as
'completed', but the failed one and all jobs runs following it will be marked
as 'failed'
- test case showing that if MifosScheduler has been initiated successfully, it
will return a valid quartz Scheduler object with all jobs registered in it
- test case showing that 'run all tasks' method will actually run all of the
tasks
- test case showing that 'run specific task' method will actually run selected
task
- test case showing that job listener will properly perform it's actions
(currently - logging) before and after each job run
was:Specific test cases' descriptions will be added later.
> Testing: Add integration/acceptance tests that fully cover new
> functionalities added by Quartz
> ----------------------------------------------------------------------------------------------
>
> Key: MIFOS-3594
> URL: http://mifosforge.jira.com/browse/MIFOS-3594
> Project: mifos
> Issue Type: Story
> Components: Batch jobs
> Affects Versions: Release E
> Reporter: Jakub Sławiński
> Assignee: Rafal Lewandowski
> Priority: Major
> Fix For: Release E - Iteration 5, Release E
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Specific test cases' descriptions will be added later.
> [02.09.10] Test cases to be added:
> - test case showing that if any batch job runs have been ommited (e.g.
> because the application was shut down), the batch system will calculate the
> dates of missing runs and execute them
> - test case showing that if previous runs of a job have failed, the batch
> system will re-run them one after another, starting with the oldest one (one
> that failed first)
> - test case showing that if a problem occured during re-running one of the
> failed jobs, all re-runs that executed successfully will be marked as
> 'completed', but the failed one and all jobs runs following it will be marked
> as 'failed'
> - test case showing that if MifosScheduler has been initiated successfully,
> it will return a valid quartz Scheduler object with all jobs registered in it
> - test case showing that 'run all tasks' method will actually run all of the
> tasks
> - test case showing that 'run specific task' method will actually run
> selected task
> - test case showing that job listener will properly perform it's actions
> (currently - logging) before and after each job run
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
