Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing experience from oneM2M - Issue 517 from w3c/wot #45

Open
egekorkan opened this issue Jul 29, 2020 · 0 comments
Open

Testing experience from oneM2M - Issue 517 from w3c/wot #45

egekorkan opened this issue Jul 29, 2020 · 0 comments

Comments

@egekorkan
Copy link
Contributor

egekorkan commented Jul 29, 2020

Coming from w3c/wot#517 on Jul 2, 2018

Tests

  • Interoperability testing
  • Conformance testing
  • Field testing

Test structure

Configuration --> Scenario --> Test Case

Configurations

  • Device to device
  • Device to cloud
  • Device via Gateway to cloud
  • ...

Scenarios

  • Discovery
  • ~Pairing
  • ...

Test Cases

One per primitive within scenario

Coverage

Specification might be to heavy to generate full coverage with test cases

Look at real products and sort them into "profiles"

Define test cases within profiles

Notes

  • Tests can help developers before starting their own implementations
  • Split specification into "features" from an architectural view to help structuring testing
  • TTCN-3 helps
  • Test cases also validate standard specification itself
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants