EdgeX QA/Test WG: Validation/Testing - Shared screen with speaker view
Cloud I updated the issue #515 and put it higher up on DevOps backlog. We should get to it when we have the chance. The good news is we do have a failing job to fix so it will be prioritized over jobs that don’t exist yet.
thank you, Lisa
This is more about unit level tests: https://github.com/edgexfoundry-holding/device-opcua-c/issues/25
What Types of API Testing Can I Do?Functionality testing — the API works and does exactly what it’s supposed to do.Reliability testing — the API can be consistently connected to and lead to consistent resultsLoad testing — the API can handle a large amount of callsCreativity testing — the API can handle being used in different ways.Security testing — the API has defined security requirements including authentication, permissions and access controls. See some API security tips for protecting vital dataProficiency testing — the API increases what developers are able to do.API documentation testing — also called discovery testing, the API documentation easily guides the user.Negative Testing — checking for every kind of wrong input the user can possibly supply
How about we divide the "types" into 2 general categories: developer tests (with unit, integration, interface, etc. subtypes) & external QA tests (with API, performance, integration, system, etc. sub-types)?
So integration is in both :P
def think integeration is explicity in external QA tests
not developer tests
some examples for robot level tags:https://stackoverflow.com/questions/22314808/how-do-you-add-tags-to-data-driven-tests-in-robot-framework