When ${NFVO_RANGE_OK} =1 ， test case 'XXX and NFVO not supporting Range Requests' should be skipped SOL003 v2.6.1 VNFPackage ManagementAPI

When testing the whole test suite 'VNFPackageContent.robot', if ${NFVO_RANGE_OK} is set to 1, both supporting and not-supporting cases will be tested. However, if ${NFVO_RANGE_OK} is set to 0, both cases will be skipped. (This situation also happens in VNFPackageArtifacts.robot)

added Plu-2021 label

added 2.6.1 label

Hi @yaoyuy

Can you please attach the log file?

log_nfvo_range_1.htmllog_nfvo_range_0.html @kraja

mentioned in commit 47e91ea9

mentioned in commit c850ccab

mentioned in commit dedae700

Hi @yaoyuy

Thnx for the logs. I've pushed the fix in both 2.6.1-fix-plu and 2.7.1-fix-plu branches.

closed

Hi @kraja I tried it again in tap. but it seems that the problem still happensde6ee3b3-5e77-4c82-ba60-752982a34149.VNFPackageManagement-API.VNFPackageArtifacts.log.html

reopened

Hi @yaoyuy

From the logs I see that the execution is not including the latest changes we made to fix this issue.

Hi @kraja I run the test again but it seems that the problem still happens. Here is the latest log c83a92eb-eb2d-4b6b-bce4-a30007604af0.VNFPackageManagement-API.VNFPackageArtifacts.log.html

mentioned in commit 17b5d056

@yaoyuy could you please kindly re-run these tests to verify if the issue is fixed?

bad news that i run it again but it isn't fixed.... Do you need the log file?

Yes please

13c5c55c-8fdd-4091-a3d4-e1fbcce56b3b.VNFPackageManagement-API.VNFPackageArtifacts.log.html I don't know if it can help you becuase i met the issue #157 (closed)

Hi @kraja Pass Execution If ${NFVO_RANGE_OK} == 1 maybe this code should be added in the keyword GET Individual VNF Package Content with explicit Range Request since we need to skip it?

mentioned in commit c73a601a

Hi @yaoyuy

Yes, you are right. The pass execution was missing.

I pushed the fix, but we will need to rebuild the TAP to make it available.

hi @yaoyuy

could you please let us know if the issue is fixed?

if we do not receive feedback by March 8th eob, we'll close the issue.

Thanks.

hi @bernini @kraja the issue is fixed in tap Thanks

closed

mentioned in commit 54207980