Discussion

Need a better end-to-end test (that exercises model loader/babel, haproxy, resources, traversal, graphadmin)

...

• Trial new robot scripts for BBS use case Keong Lim 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2184

   or
• develop AAI best practises Contributing To AAI Best Practise
• write up new tutorial AAI Tutorial-Making and Testing a Schema Change - Dublin

4th Mar:

• Trial for CCVPN use case 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2208

  develop AAI best practises Contributing To AAI Best Practise
• write up new tutorial AAI Tutorial-Making and Testing a Schema Change - Dublin

Procedure

Follow testsuite Readme for setup: https://gerrit.onap.org/r/gitweb?p=testsuite.git;a=blob;f=README.md;hb=HEAD

...

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2208

   / https://gerrit.onap.org/r/79583
• Updated suggestions from gerrit reviews:

  • Brian Freeman

    if the intent is to have a aai-backwards-compatibility-v14.robot function that would get added to each release as the version number increases then I guess you need to create aai-[something]-v14, aai-something]-v16 etc. Not sure these are end to end tests becuase we arent testing that a Dublin vFW works end to end with v14 API's when most components will be calling the v16 APIs. If its simply AAI regression as part of verify/merge CSIT jobs then we should have a nomenclature with CSIT in the filename to distribution End to End tests from CSIT tests. aai-csit-v14 , aai-csit-v11 ?
    Technically even Amsterdam had a mixture of versions supported so it seems like you may want to be testing by version not by release package name ?

  • Daniel Rose

    i looked over catherines presentation. I think if we are going to support csit type tests, i am ok. i think we need to put them in testsuites/<app> and tag those tests as csit. I still also dont think we should put release specific code in here though. I think supporting 2 versions of aai schema is ok if you ar releasing that, but calling something as casablanca is not - the branch should always work with the release it is.

  • Keong Lim
    AAI team did have an idea that our tests could be used to diagnose installation problems, e.g. pulling the wrong version and wondering why it doesn't work. So as part of the "sanity integration" testing, we would publish these tools/scripts for use on any installation (development, test labs, production, etc), not just the latest.

    I will update a new patchset.

    The naming can be updated. Wasn't sure if the release names were more familiar than the API version numbers.