Opened 12 years ago
Last modified 11 years ago
#363 closed task
Enhancement of petascope regression test suite — at Version 12
Reported by: | abeccati | Owned by: | Nikolche Kolev |
---|---|---|---|
Priority: | major | Milestone: | 8.5 |
Component: | systemtest | Version: | 8.4 |
Keywords: | Cc: | Dimitar Misev, Piero Campalani, Alireza, Jinsongdi Yu | |
Complexity: | Medium |
Description (last modified by )
As part of the proposed projects we have regression test refactoring
Wrt regression testing we need improvement especially with petascope tests (documented here)
Most compelling is the inclusion of an oracle or similar structure for evaluating query output and enable also queries that purposefully generate errors to be part of successful test cases.
Currently the test system is under improvement and the reference test.sh script is the one into test_wcps directory. The development direction is to make that script flexible enough to be directly linked from the other directories (test_wms, test_wcs) and run on the local data on these. This approach is already used in the test_wms part and should be adopted also for the test_wcs as soon as it is proven stable.
Change History (12)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Note I've updated a bit the test page at wiki:RasdamanTestSuites#Petascopetests
The configuration file for petascope and the whole systemtest now is source:systemtest/conf/test.cfg
comment:3 by , 11 years ago
As soon as the oracle-based testing system is set up, as a next step we should add (many) error-prone queries and verify they actually return an error/exception (this will help us reviewing error messages and identifying cumbersome ones, e.g. see #394).
comment:4 by , 11 years ago
That should go in another ticket Piero, I don't think Nikolce has the background to add such tests.
comment:5 by , 11 years ago
Yes, it was general next-step, not Nikolce's next step
It was a note, then we can either create a new ticket or go on with this one, whatever.
comment:6 by , 11 years ago
Status: | new → assigned |
---|
I strongly second Piero's proposal and created #396 for that purpose (we should keep tasks/ticket as "atomic" tasks as much as we can to ease management)
Let's finalize infrastructure first with this ticket.
@nkolev: Please "accept" the ticket (accept option at bottom of modify ticket) so we can track active assignment.
comment:7 by , 11 years ago
Status: | assigned → accepted |
---|
comment:10 by , 11 years ago
Complexity: | Easy → Medium |
---|---|
Description: | modified (diff) |
Also WMS tests are missing, basic ones should be included. Meanwhile patch submitted to master (2013-07-23 14:02:17) for WMS inclusion: links directly to the test.sh engine script.
comment:11 by , 11 years ago
Included first test passing getCapabilities and loading WMS test data "mean_summer_airtemp" as laid out by Piero at http://rasdaman.org/wiki/WmsImportTools
Please note that the WMS engine is the same as the wcps one (to be used as refernce) and the patch (2013-07-23 19:31:01) extends it to detect service name according to the base directory where it is linked from (e.g. test_wms). This can be reused for all services to ease maintenance.
comment:12 by , 11 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Milestone: | → 8.5 |
Status: | accepted → assigned |
Changing to assigned since some changes have been committed meantime and no active progress seen in some time. nkolev please re-accept when working on it again and read the updated doc at RasdamanTestSuites to get aligned.
Adding also Jin (systemtests component owner) in cc for overall test systems coordination.
Note that I have submitted some systemtest refactoring patch, you should do your work after applying that on.