Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Revised May 28, 2019


Table of Contents

Table of Contents

...

The following product and infrastructure items that will be needed:

Deliverable

Lead

Test plan for each type of service

QA

Black box tests for each type of service based on the test plan

QA + Dev

Parameterize black box tests with the git location and access credentials so the certification authority can use/automate existing tests and point them to location that may not be under our control (submitter provided repository)

Dev

Performance/longevity tests for 24 hour exercise of service

Dev

Test of the certification tests.

  • Confirm black box tests are valid for certification. I.e., the cert tests may have slightly different needs than dev tests.
  • Confirm that certified services are truly interoperable (important for credibility of cert program)

QA

Process and instructions for executing tests

  • For self-assessment users
  • For certification testers

QA + Certification

Independent infrastructure that can be used by the certification testing team

    • Infrastructure only accessible by certification testers
    • Each test would be scripted to initialize from scratch
    • Store results of testing
    • Environment to be protected during period of performance/longevity testing (~24-36 hours)
    • May need multiple instances running at the same time

DevOps

Repository only accessible to certification testing team to store raw test results and results report (for use in the event of later question)

DevOps

Location for public to obtain self-assessment tests and documentation

DevOps

Clean up process following completion of certification process

  • Delete submitter code/artifacts
  • Store results

DevOps + Certification


Other notes:

  • Consider using existing device services to confirm process and that they can be certified (test our own dog food)
  • Assumption that some submitters will want to provide their code from a private repository. Need to investigate how to script pulling the code (private certs?) and running tests.

...

The following items that will be needed to execute the certification process:

Deliverable

Responsible

Application form to gather details about the requester and code being submitted

Certification

Legal agreement to confirm rules for code handling by certification authority and rights and responsibilities for use of Certification by requestor

Certification + LF

Code submission process

  • Specification of format/content/code
  • Intake process (controlled access)

Certification

Record and store testing results/observations

Certification + DevOps

Report of failed test with information on failure and process for remediation

Certification

Create formal certification test results document

Certification

Issue formal letter of certification or failure to submitter

Certification

Periodic reports of certification learnings (anonymized) to the community

Certification

Other notes:

  • The certification testing process and results are private between submitter and EdgeX Foundry until the process is completed.

...

In order to achieve the full benefits of the certification program it must be seen as having value and momentum. The following items will be helpful in that effort:

Deliverable

Responsible

Web page(s) about certification

  • Information about certification program and how to apply
  • Listing of certified EdgeX components

Marketing

Coordinate with submitter on when they want to make public announcement

Marketing

Joint press release template that can be used to announce new certified component

Marketing

Periodic follow up with users of certified components to confirm value and gather quotes that could be used for additional promotion

Marketing

External Certification Authority

...