Run minimal "smoke tests" where possible for calculators without specific QA tests

Bug #943890 reported by Paul Henshaw
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenQuake (deprecated)
Fix Released
Critical
Unassigned

Bug Description

Created from bug #906911

As a "stop-gap" solution, for each calculator which does not have a specific QA test but which does have a demo which runs to completion in a reasonable time frame, simply run the demo and check that it does not crash.

Revision history for this message
Paul Henshaw (paul-sl-henshaw) wrote :

See also bug #947149

Revision history for this message
Paul Henshaw (paul-sl-henshaw) wrote :

See also bug #947155

Changed in openquake:
assignee: nobody → Andrea Cerisara (andreacerisara-b)
status: New → In Progress
importance: Undecided → Critical
Revision history for this message
Lars Butler (lars-butler) wrote :

Hazard QA Coverage:

classical:
  - end-to-end? Yes
  - DB? Yes
  - XML? Yes
  - demo suitable for QA test? Yes

event-based:
  - end-to-end? No
  - DB? No
  - XML? No
  - demo suitable for QA test? No. 1) Demo includes Risk calculations. 2) Source model contains over 100 sources.

scenario:
  - end-to-end? Yes
  - DB? No
  - XML? No
  - demo suitable for QA test? No. 1) Demo includes Risk calculations.

disaggregation:
  - end-to-end? Yes
  - DB? N/A (no disaggregation results are currently stored in the database)
  - XML? Yes
  - demo suitable for QA test? Yes

UHS:
  - end-to-end? Yes
  - DB? Yes
  - XML? No. (Only file creation is covered; the actual contents are not checked in the current QA tests.)
  - demo suitable for QA test? Yes

Revision history for this message
Andrea Cerisara (acerisara) wrote :

The pull request https://github.com/gem/oq-engine/pull/717 contains an end-to-end smoke test for the event-based calculator (hazard+risk). It doesn't check the results, but should be ok for this bug.

John Tarter (toh2)
Changed in openquake:
milestone: none → 0.6.1
Changed in openquake:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.