[IEC-34] [IEC][SEBA] Verify latest cord-tester on amd64 in preparation for updating on arm64 Created: 30/Mar/20  Updated: 06/Apr/20  Resolved: 06/Apr/20

Status: Done
Project: Integrated Edge Cloud
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: Ciprian Barbu Assignee: Valentin Radulescu
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File siab_make_run_tests.txt    
Issue Links:
Blocks
blocks IEC-35 [IEC][SEBA] Update and refresh testin... In Progress

 Description   

Since a lot of time has passed since my last attempt to integrate SIAB testing into IEC, we need to re-asses the current situation. SEBA has also advanced upstream, some things have changed, others might have been completely refactored. Even more, we are not yet based on the latest SEBA version, since upstream still works on the tip and things are not always stable.

We will benefit from making a hands-on attempt on running the SiaB tests on our own SEBA-in-a-Box setup in ENEA's private lab, just to see where we are with our reference commit.

Once we get the tests and the framework passing we will move to arm64 and make the necessary adjustments.



 Comments   
Comment by Valentin Radulescu [ 06/Apr/20 ]

Hi,

Running make run-tests was successful, closing this CR.

Valentin Radulescu

Comment by Valentin Radulescu [ 31/Mar/20 ]

Hi,

I run the test in our SIAB deploy. Basically, the tests does the following in automation-tools/seba-in-a-box, using make run_tests target:
mkdir -p $(WORKSPACE)/cord/test
cd $(WORKSPACE)/cord/test && git clone https://gerrit.opencord.org/cord-tester
cd $(WORKSPACE)/cord/test/cord-tester/ ;\
make venv_cord; source venv_cord/bin/activate ; set -u;\
cd src/test/cord-api/Tests/WorkflowValidations/ ;\
robot $(PYBOT_ARGS) --removekeywords wuks -e notready -i $(TESTTAGS) -v VOLTHA_DIR:$(WORKSPACE)/cord/incubator/voltha SIAB.robot

Generated at Sat Feb 10 06:02:18 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.