# Integration and test monitoring architecture Part I

XMLWordPrintable

## Details

• Type: Epic
• Status: Done
• Resolution: Done
• Fix Version/s: None
• Component/s:
• Labels:
None
• Epic Name:
sqre-metrics-infra-capture-one
• Story Points:
100
• WBS:
02C.01.02
• Team:
SQuaRE
• Cycle:
Winter 2016

## Description

[retitled to better capture cycle scope]

Develop and deploy a layer to capture the outputs, initially numeric,
of integration testing afterburners such as sdss_demo, hsc_demo, and
others developed this cycle. Also capture meta-information such as
execution time and memory footprint. Propose log format to standardise
production of such informations. Investigate notification system based
on trending away from expected values. Investigate data provisioning
of integration tests such as storage of test data in GithubLFS.

[75% JMP 25% JH]

## Activity

Hide
Michael Wood-Vasey added a comment -

Where does work on designing this test monitoring architecture stand? I don't see an issue related to this Epic that is something like "Design Layer". Should that be added? To whom who it be assigned?

I'd like to start connecting the validation outputs in validate_drp to a test harness.

What kind of outputs should validate_drp produce for this test harness?

Show
Michael Wood-Vasey added a comment - J Matt Peterson [X] Joshua Hoblitt David Nidever [X] Frossie Economou Where does work on designing this test monitoring architecture stand? I don't see an issue related to this Epic that is something like "Design Layer". Should that be added? To whom who it be assigned? I'd like to start connecting the validation outputs in validate_drp to a test harness. What kind of outputs should validate_drp produce for this test harness?
Hide
Frossie Economou added a comment -

Hi Michael Wood-Vasey, we're stilll prototyping for this part of the harness, which is intended to capture scalars, the interface is going to be via structured log messages, so if you will just output JSON with your parameters of interest for now, we shouldn't have to make too many changes later.

Show
Frossie Economou added a comment - Hi Michael Wood-Vasey , we're stilll prototyping for this part of the harness, which is intended to capture scalars, the interface is going to be via structured log messages, so if you will just output JSON with your parameters of interest for now, we shouldn't have to make too many changes later.
Hide
Michael Wood-Vasey added a comment -

Thanks for the clarification and suggestion to output something in JSON.

Will do as: DM-4957

Show
Michael Wood-Vasey added a comment - Thanks for the clarification and suggestion to output something in JSON. Will do as: DM-4957
Hide
J Matt Peterson [X] (Inactive) added a comment -

Completed. Any additional work has been moved to new epics in other cycles.

Show
J Matt Peterson [X] (Inactive) added a comment - Completed. Any additional work has been moved to new epics in other cycles.

## People

• Assignee:
J Matt Peterson [X] (Inactive)
Reporter:
Frossie Economou
Watchers:
Frossie Economou, J Matt Peterson [X] (Inactive), Michael Wood-Vasey