Opened 11 years ago

Closed 8 years ago

#513 closed enhancement (fixed)

Import functions in systemtest

Reported by: Piero Campalani Owned by: Dimitar Misev
Priority: minor Milestone: Future
Component: systemtest Version: development
Keywords: import functions Cc:
Complexity: Medium

Description

Import functions in the systemtests are all very similar and should be refactored so to call a single parametrizable function, at least one for each coverage type (i.e. multipoint, grid, …).

$ grep "import_.*()" ./systemtest/util/petascope.sh  
function import_eobs()
function import_rgb()
function import_mr()
function import_irr_cube_1()
function import_mst()
function import_petascope_data()
function import_pointcloud_data()

Change History (4)

comment:1 by Dimitar Misev, 11 years ago

I have a more generic petascope import function here, I'll try to integrate it into the petascope.sh

comment:2 by abeccati, 10 years ago

I have also noticed that petascope import do not make use of rasimport. While it is fine for the beta stage (since it is not in sync), I think it's better to make use of it to ensure it stays in the loop of testing. As a nice side effect it makes importing geodata mostly oneliners. As a not nice side effect it makes petascope tests dependant on its correctness.

comment:3 by abeccati, 10 years ago

Type: defectenhancement

Also does not really seem a defect

comment:4 by Dimitar Misev, 8 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.