Testing Ideas - GeoscienceAustralia/egeodesy GitHub Wiki

Geodesy - Tests - ideas - 1/6/16

Relationships

  • Site -> *Setup
  • Setup* <-> *EquipmentInUse
  • Site -> *Node
  • Setup -> *Node
  • Node* -> Position id=fourCharacterId
  • CorsSite id=fourCharacterId -> Monument

Objects and tests:

CorsSite -

  • String fourCharacterId
  • String domesNumber
  • Monument monument
  • String geologicCharacteristic
  • String bedrockType
  • String bedrockCondition

Equipment (Clock, GnssAntenna, GnssReceiver, HumiditySensor)

  • String type
  • String equipmentType
  • String manufacturer
  • String serialNumber
  • String aspiration (HumiditySensor)

EquipmentConfiguration

  • Integer equipmentId
  • Date configurationTime
  • - is it bound by the owning Setup.effectivePeriod
    

EquipmentInUse

  • Integer equipmentId
  • Integer configurationId
  • EffectiveDates period
  • - test that becomes effective
    
  • - test bounds EquipmentConfiguration.configurationTime
    

Monument

  • String description
  • String foundation
  • String markerDescription
  • String height

Node

  • Integer siteId

  • Integer setupId

  • EffectiveDates effectivePeriod

    • is the effectivePeriod.from >= (site.dateInstalled and setup.effectivePeriod.from) and the effectivePeriod.to > site.dateInstalled and <= setup.effectivePeriod.to AND invalidated is true

    • and vice-versa

  • Boolean invalidated

Position

  • String fourCharacterId
  • Integer nodeId
  • Integer datumEpsgCode
  • Double x
  • Double y
  • Date epoch
  • Date asAt
  • Integer positionSourceId

Setup

  • Integer siteId

  • String name

  • EffectiveDates effectivePeriod

  • Boolean invalidated

    • is this false when all child Nodes.invalidated == false
  • List equipmentInUse

    • when (a new piece of equipement is added | a piece of equipment is changed) to create a new setup, is the equipment in the new setup the same as in the old but for the new or changed item

Site

  • String name
  • String description
  • Date dateInstalled

WeeklySolution

  • Date asAt
  • Date epoch
  • String sinexFile

Other Tests

Sitelog validated

- invalid schema - fail

- invalid codelists - fail

- dates not overlapping - fail

- ...

- else succeed

Sitelog upload

  • new site

    • are all items created that are expected (see below) and don't belong to anything else (eg. EquipmentInUse, Nodes which have a many:one relationship with Setup and Site) -- items created are: ..
  • same site, new configuration (new equipment)

    -- expect these to stay the same - ...

    -- expcet these to change - ...

    -- expect these to be new - ..

  • same site, new configuration (modified equipment)

    -- expect these to stay the same - ...

    -- expcet these to change - ...

    -- expect these to be new - ..

  • same site, same configuration

    -- expect nothing to change