...
20th Feb: Move from CSIT to Robot. See PTL 2019-02-19 presentation https://wiki.onap.org/download/attachments/53249527/Dev%20Testing_Enhancement%20for%20Dublin_V2.pptx?version=1&modificationDate=1550580552000&api=v2
21st Feb:
- Trial new robot scripts for BBS use case Keong Lim
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2184 - develop AAI best practises Contributing To AAI Best Practise
- write up new tutorial AAI Tutorial-Making and Testing a Schema Change - Dublin
...
- Updated suggestions from gerrit reviews https://gerrit.onap.org/r/79583:
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.
...
| Code Block | ||
|---|---|---|
| ||
cd testsuite # cloned from git/gerrit repository # run the AAI scripts from the right directory #robot add path to--argumentfile my-aai.txt robot/library/, and sub-directoriestestsuites/aai/ # refersoutput tolooks resourceslike under robot/resources/, assets under robot/assets, etc # make sure the referenced python library modules are installed # inject the necessary global variables in my-aai.env robot \ --pythonpath robot/library/:robot/library/eteutils \ --variablefile my-aai.env \ robot/testsuites/aai/ # output looks like this ------------------------------------------------------------------------------ Aai.Aai-Regression-Test-V14 :: AAI CSIT-style regression tests for... | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed ============================================================================== Aai | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed ============================================================================== Output: D:\ONAP\testsuite\testsuite\output.xml Log: D:\ONAP\testsuite\testsuite\log.html Report: D:\ONAP\testsuite\testsuite\report.html this ============================================================================== Aai ============================================================================== Aai.Aai-Regression-Test-V14 :: AAI CSIT-style regression tests for CCVPN - ... ============================================================================== Connectivity test case | PASS | ------------------------------------------------------------------------------ Aai.Aai-Regression-Test-V14 :: AAI CSIT-style regression tests for... | PASS | 1 critical test, 1 passed, 0 failed 1 test total, 1 passed, 0 failed ============================================================================== Aai | PASS | 1 critical test, 1 passed, 0 failed 1 test total, 1 passed, 0 failed ============================================================================== Output: D:\ONAP\testsuite\testsuite\output.xml Log: D:\ONAP\testsuite\testsuite\log.html Report: D:\ONAP\testsuite\testsuite\report.html # argumentfile my-aai.txt contains --pythonpath robot/library/:robot/library/eteutils --variable GLOBAL_AAI_USERNAME:AAI --variable GLOBAL_AAI_PASSWORD:AAI --variable GLOBAL_AAI_SERVER_PROTOCOL:https --variable GLOBAL_INJECTED_AAI1_IP_ADDR:xxx.yyy.zzz.aaa --variable GLOBAL_AAI_SERVER_PORT:30233 --loglevel DEBUG # for debugging of error messages, use a browser to view log.html and report.html |
20th June: See also update to Jinja templating:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key TEST-158 - https://gerrit.onap.org/r/c/testsuite/+/90197
- https://gerrit.onap.org/r/c/testsuite/+/90235
26th June: Robot testing for Sparky sanity tests
- Use AAI robot scripts to create an object, e.g. vpn-binding, i.e. do not do Teardown steps that delete the objects at the end of the test
- Login to Portal and navigate to AAI UI (Sparky)
- Use Sparky to browse the object, thus providing minimum test of sparky-fe, sparky-be, search-data-service microservices
- See attachments on 2019-06-20 AAI Developers Meeting
| Code Block |
|---|
Add to hosts file:
<ONAP.IP.address> portal.api.simpledemo.onap.org
<ONAP.IP.address> vid.api.simpledemo.onap.org
<ONAP.IP.address> sdc.api.fe.simpledemo.onap.org
<ONAP.IP.address> portal-sdk.simpledemo.onap.org
<ONAP.IP.address> policy.api.simpledemo.onap.org
<ONAP.IP.address> aai.api.sparky.simpledemo.onap.org
<ONAP.IP.address> cli.api.simpledemo.onap.org
<ONAP.IP.address> aaf-onap-test.osaaf.org
<ONAP.IP.address> aai.ui.simpledemo.onap.org
Install onap_root.crt into Windows and Firefox trusted authorities
Visit portal website: https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/login.htm
|