aboutsummaryrefslogtreecommitdiffstats
path: root/packages/arquillian-unit-tests
AgeCommit message (Collapse)AuthorFilesLines
2017-10-03Increase the wait for mariadbDeterme, Sebastien (sd378r)1-2/+2
Increase the number of polling done to verify that mariadb is up before starting the mso container Change-Id: I0fdab8aaa0f17078f9a94700e7918dd30aab3407 Issue-ID: SO-171 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-10-02Disable non-working integration testsRob Daugherty1-4/+4
These will need to be fixed soon, but the first step is to have a working environment again. I am also removing obsolete versions of camunda sql scripts. Change-Id: I5817be8a879505fa4f146d2e49b26a305ece356a Issue: SO-171 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-10-02Merge "Fix the arquillian framework"Seshu Kumar M2-401/+372
2017-10-02Fix the arquillian frameworkDeterme, Sebastien (sd378r)2-401/+372
Arquillian framework was broken due to bad dependency used during ITS Change-Id: I2c865b429af45511d778d11d77a16704b49fdef6 Issue-ID: SO-171 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-10-01URL mismatch in mso.sdnc.propertiesRob Daugherty1-1/+4
There was a mismatch between the "sdncurls" definitions in the environment files (e.g. mso-docker.json) and the property file template (mso.sdnc.properties). This commit adds missing "sdncurls" to the arquillian unit test environment. Issue: SO-123 Change-Id: I538c9df71fec6e9368d4a984eb82f58ec3b0c545 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-09-27Update POM to inherit from oparentRob Daugherty14-0/+278
Issue: SO-71 Change-Id: I91d503b52909cfcb62ca4b5cd93f6cfc70d6eb24 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-09-21SO Failed Robot Health CheckRob Daugherty1-1/+2
There were several issues. The wrong jackson provider was being selected, which caused the exception, so we fixed that. Then we discovered that a a URN mapping was missing, so we added that. Then we found that the healthcheck wouldn't work because it's trying to check the default process engine, which does not exist. We commented out that part of the healthcheck to be able to resolve this high priority issue. A new low priority issue will need to be created to follow up. Change-Id: I327612a147333eeecd44915942cecd13959c4717 Issue-id: SO-139 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-09-081710 Rebase - Second AttemptArthur Martella7-45/+70
This commit rebases changes from openecomp-mso/internal-staging-1710 up to and including this codecloud commit: 54483fc6606ddb1591a2e9da61bff8712325f924 Wed Sep 6 18:12:56 2017 -0400 Rebasing was done on a branch on top of this commit in so/master in ONAP: 93fbdfbe46104f8859d4754040f979cb7997c157 Thu Sep 7 16:42:59 2017 +0000 Change-Id: I4ad9abf40da32bf5bdca43e868b8fa2dbcd9dc59 Issue-id: SO-107 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-5/+5
There are Linux Foundation rules (enforced by nexus) that I still don't really understand. I'm convinced this is absolutely true: The groupId of every artifact in a project MUST begin with: org.openecomp.<project> --or-- org.onap.<project> The top-level artifact is no exception. So for example, this is NOT allowed: <groupId>org.openecomp</groupId> <artifactId>so</groupId> Here's what I'm trying now. The top level pom will contain: <groupId>org.openecomp.so</groupId> <artifactId>so-parent</artifactId> Child modules will contain: <parent> <groupId>org.openecomp.so</groupId> <artifactId>so-parent</artifactId> <version>1.1.0-SNAPSHOT</version> </parent> <groupId>org.openecomp.so</groupId> <artifactId>some-child-artifact</artifactId> Note that the groupId for the direct child module will be the same as the groupId for its parent. Issue: SO-21 Change-Id: I0d3cd2eb7a1883e23e3c0878ee7fa3dd4a7d55b2 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-08-01Failed to deploy so artifacts in nexusRob Daugherty1-5/+5
More problems encountered since mso repos were renamed. We now have found that this declaration in the top-level so pom causes the deploy to fail with a 403 Forbidden error: <groupId>org.openecomp</groupId> <artifactId>so</artifactId> We are changing this to: <groupId>org.openecomp.so</groupId> <artifactId>framework</artifactId> Issue: SO-21 Change-Id: I4e21d689c73c5071bde725127bb81482ce3d91f9 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-07-19Fix artifact group IDs (org.openecomp.so)Rob Daugherty1-5/+5
Since the repositories were renamed from "mso" to "so" the artifact group IDs in the poms must be updated to match. Issue: SO-39 Change-Id: I617fe738a77d0f6c1d1cc0ac9474fb753f4e234c Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-05-09[MSO-8] Additional fixes for the second rebaseDeterme, Sebastien (sd378r)1-4/+4
DB fixes + BPMN flows and groovy fixes + Fix issue with CloudConfig file not reloaded properly when it's wrong (JSON error or model hierarchy mistake) at MSO startup Change-Id: I2853030b78499e2a761706b643ea210955e72de3 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com> [MSO-8] Restore files removed in patch set 2 Those groovy files must be there Change-Id: I9a47ac3d9c8fc06774a1b8f518491b1b0b00af04 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-05-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)5-1122/+1126
Second rebase containing additional features for MSO + total reworking of the BPMN structure + Notification flow can now be added at the end of some BPMN flows Change-Id: I7e937c7a0ba1593ca85e164a093f79c7e38b6ce0 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-04-11[MSO-8] Update the maven dependencyxg353y30-610/+679
Update the maven depenency for sdc-distribution-client to cooperate with the sdc changes. Change-Id: I2da936e5c40cb68c7181bb78307192dd5655b5dc Signed-off-by: xg353y <xg353y@intl.att.com>
2017-03-13Update to version 1.1.0ChrisC1-1/+1
Change-Id: Id054e7a04ce88450c3cfe108c8259c4d287681c8 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-03-06Prepare for Release 1.0.0ChrisC1-1/+1
Change-Id: I54ab6edea94e61dd5dbfdb945bda2f51b5d8fc39 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-02-14Update SoapUI tests for APIH Infraxg353y3-88/+242
Adding more failure test cases in the APIH Infra SoapUI file. Update the necessarily file to expose arquillian mariadb port and download mariadb driver so that it could be used in SoapUI test cases. Change-Id: I9c3028128530878b432b521aebd0993f1c9e7dd5 Signed-off-by: xg353y <xg353y@intl.att.com>
2017-02-10SoapUI tests for APIH Infraeh552t2-32/+32
Replaces tabs by spaces in MsoRequest.java removed references to com.att in endpoints Change-Id: I6e49fa9d82669d3e205023bf16a40f48e4f56b12 Signed-off-by: eh552t <eh552t@intl.att.com>
2017-02-09SoapUI tests for APIH Infraeh552t4-20/+1757
Added some soapUI tests for testing APIH Infra in Arquilian. Some bug fixes in the Tenant Adapter and VNF adapter SoapUIs. BugFix in case of bad ModelType in a request we gor null pointer Exception. Change-Id: Icf9b8fc344d15860ac8dd11984894b07ecf5b085 Signed-off-by: eh552t <eh552t@intl.att.com>
2017-01-31Updating dependent artifact version in a few pom.xmlChrisC1-1/+1
Change-Id: I1b8d5e48da3ac4d1257214dab38706302d0acd10 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-01-31Initial OpenECOMP MSO commitChrisC170-0/+20945
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>