aboutsummaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2020-08-19DH install/uninstall improvementsShadi Haidar2-56/+233
Install workflow changes: -Use inventory blueprint (BP) typeId when uploading BP to Cloudify/CFY -Set global visibility when uploading BP to CFY for multi-tenant access -Re-use BP if it exists in CFY rather than alawys uploading a new BP -Do not add a new service in inventory anymore Un-Install workflow changes: -Retreive associated BP against the deployment -Check if any other deployments still exist against the BP -If no associated deployments, get the associated tenant for the BP -Only delete BP if there are no more associated BPs -Do not remove associated service from inventory (it won't exist) Coverage summary Statements : 78.01% ( 997/1278 ) Branches : 56.45% ( 302/535 ) Functions : 74.89% ( 164/219 ) Lines : 78.54% ( 988/1258 ) Issue-ID: DCAEGEN2-2022 Signed-off-by: Shadi Haidar <sh1986@att.com> Change-Id: I9cb197edc3a0276c5ca95f9c936fc7300d849f56 Signed-off-by: Shadi Haidar <sh1986@att.com> Signed-off-by: Shadi Haidar (sh1986) <sh1986@att.com> Signed-off-by: Shadi Haidar <sh1986@att.com>
2020-02-284.3.0/6.1.0 deploy-handler - policyVersion as str4.3.0Alex Shatov1-58/+71
- external version 4.3.0 - internal version 6.1.0 for code change - no API change - deployment-handler now expects the policyVersion as semver or any string to support for DMaaP MR update notification from the new PDP - changed Dockerfile to use the alpine base image to reduce the footprint - brought the latest packages except zip lib - added package-lock.json to freeze the dependencies - latest log4js - change of configuration file format - fixed call to cloudify API /node-instances added &_sort=id to make the pagination consistent - changed uuid/v4 to uuid.v4() to avoid the deprecation warning - unit test = coverage by nyc now = on policy API - assert all expected nock calls are done - integration testing with the latest policy-handler (DCAEGEN2-1851) and the new policy-engine is requested unit test coverage summary Statements : 83.78% ( 1023/1221 ) Branches : 62.95% ( 333/529 ) Functions : 84.35% ( 194/230 ) Lines : 84.18% ( 1011/1201 ) Change-Id: I174aa0b8804af0378755de86be833b0b763ddc1d Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-2085
2019-03-26Add health and service endpointsShadi Haidar2-1/+278
4.0.0 deployment-handler Upgraded cloudify api from 2.1 to 3.1 due to new cloudify /status api Requires upgrading Cloudify to 4.x Added 2 APIs to check health of DH itself and to Inventory and Cloudify Coverage summary Statements : 80.75% ( 994/1231 ) Branches : 57.74% ( 302/523 ) Functions : 81.13% ( 172/212 ) Lines : 81.26% ( 984/1211 ) Issue-ID: DCAEGEN2-1127 Change-Id: Ic851a576eed668016f6cfe956f0f1880a65e1065 Signed-off-by: Shadi Haidar <sh1986@att.com>
2019-02-053.2.0/5.2.0 - fixed zip folder bug by admzip libAlex Shatov3-25/+41
- external version 3.2.0 - internal version 5.2.0 for code change - no API change - fixed the zip folder bug when sending the blueprint to cloudify = this bug was preventing the opening of the blueprint in cloudify UI because the folder record was not properly formatted by admzip lib 0.4.7 - upgraded adm-zip lib to the latest version 0.4.13 - unit tested the zipping of the blueprint file under subfolder without having the subfolder record in zip = manual unzip in linux shows proper subfolder/file structure = automatic unzip is not supported by the old ubuntu = would need upgrading the node.js/ubuntu and installing unzip for proper testing - see code comments in unit-test - zip file created by admzip unzips properly both in linux and in Windows = zip still has some header warnings, but not critical unit test coverage summary Statements : 80.94% ( 943/1165 ) Branches : 58.22% ( 294/505 ) Functions : 81.28% ( 165/203 ) Lines : 81.48% ( 933/1145 ) Change-Id: I48e44f025c21ef51de5a7422c8db9433581c787f Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-855
2018-12-063.1.0/5.1.0 - check for finished deploymentAlex Shatov2-7/+98
- external version 3.1.0 - internal version 5.1.0 for code change - no API change - check for finished deployment creation - success or failure - stop querying cloudify manager on failed deployment creation - use optional $CONSUL_URL to get url of consul - improved info used for audit and logging and responses - added more unit tests unit test coverage summary Statements : 80.99% ( 946/1168 ) Branches : 58.22% ( 294/505 ) Functions : 81.28% ( 165/203 ) Lines : 81.53% ( 936/1148 ) Change-Id: I831cd0db0d2e148e6da4c9190495aacf72e2d39c Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-929
2018-11-09R4 tag updateVijay Venkatesh Kumar1-1/+1
Change-Id: Iafa10f8707e3e2db318258dbfbccc65a6b5e8208 Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com> Issue-ID: DCAEGEN2-937
2018-09-12Check deployment creation before installShadi Haidar1-0/+23
Unit Test Code Coverage: Statements : 76.85% ( 893/1162 ) Branches : 52.99% ( 275/519 ) Functions : 78.68% ( 155/197 ) Lines : 77.21% ( 884/1145 ) Issue-ID: DCAEGEN2-754 Change-Id: Id8f3fa26e8ece7e9099145ea20034829a1ad7d13 Signed-off-by: Shadi Haidar <sh1986@att.com>
2018-08-033.0.0 new dataflow on policy-update and catchupAlex Shatov2-32/+31
- external version 3.0.0 - internal version 5.0.0 for API and code - changed API and functionality - new dataflow - new dataflow between policy-handler and deployment-handler on policy-update and catchup = GET /policy - returns the deployed policy_ids+versions and policy-filters = PUT /policy updates policies on deployed components = new message format for policy-update and catchup = matching by policy_id+version and policy_filter_id only - removed POST to /policy - the obsolete API = removed the 'smart' matching of the policies by policy-filter -- it is done by the policy-handler now Coverage summary Statements : 77.06% ( 870/1129 ) Branches : 53.55% ( 264/493 ) Functions : 78.53% ( 150/191 ) Lines : 77.45% ( 862/1113 ) Change-Id: I5409f32e1acd4870f1d74b466902a796fa10f6c7 Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-492
2018-07-16Update release tagLusheng Ji1-1/+1
Issue-ID: DCAEGEN2-499 Change-Id: Iec19c1d8412b6e40bd66ebc69d9a0cbf46202368 Signed-off-by: Lusheng Ji <lji@research.att.com>
2018-05-092.1.4 - fixed "value" argument is out of boundsAlex Shatov1-2/+56
- using the original "adm-zip": "0.4.7" because the latest "adm-zip": "0.4.9" is broken - external version 2.1.4, internal version 4.4.4 - unit test code coverage Statements : 83.99% ( 939/1118 ) Branches : 62.75% ( 320/510 ) Functions : 81.15% ( 155/191 ) Lines : 84.13% ( 928/1103 ) Change-Id: I7e82b1d7a51c562eb88cffbc12a0bfa0d92eebee Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-487
2018-05-07fixed 413 "request entity too large" for /policyAlex Shatov1-41/+35
- increased the message limit to 150mb on policy-update API to avoid 413 on catchup messages from policy-handler - external version 2.1.3, internal version 4.4.3 - unit test code coverage Statements : 84% ( 940/1119 ) Branches : 62.75% ( 320/510 ) Functions : 81.15% ( 155/191 ) Lines : 84.15% ( 929/1104 ) Change-Id: Iafd27b37fde6b0a310f2ba805f505f380b58ec1f Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-491
2018-05-04fixed 500 "value" argument is out of boundsAlex Shatov2-2/+3
- convert the EOL to linux "\n" in the blueprint before zipping and sending to cloudify to avoid crashing when the blueprint is windows "\r\n" or mac "\r" based - on catching the exception - log the stack - added logger.info that replaced the logger.debug in a variety of places - external version 2.1.2, internal version 4.4.2 - unit test code coverage Statements : 84.26% ( 942/1118 ) Branches : 64.14% ( 322/502 ) Functions : 81.68% ( 156/191 ) Lines : 84.32% ( 930/1103 ) Change-Id: I9f5f28ddd5d143ca4903316c9199df7d27682143 Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-487
2018-04-064.4.1 deployment-handler -unit tests 84% coverageAlex Shatov4-125/+569
- more logging on metrics - log both req and res - unit tests of policy-update API - log timing and messaging in unit tests - code coverage 84.28% Statements 938/1113 65.51% Branches 321/490 81.58% Functions 155/190 84.34% Lines 926/1098 Change-Id: I3587135ceac76b291f83753441421a917a8b8bdf Signed-off-by: Alex Shatov <alexs@att.com> Issue-ID: DCAEGEN2-258
2018-02-12Update license textLusheng Ji1-1/+1
Change-Id: Idff7ac3c209823d0f96d4b942363d41b9e39325a Signed-off-by: Lusheng Ji <lji@research.att.com> Issue-ID: DCAEGEN2-325
2018-02-05fix copyright from 2018 to 2017-2018Alex Shatov1-1/+1
Change-Id: I87f4438774a5e8b65bc8ceba83893a717a8a907f Issue-ID: DCAEGEN2-249 Signed-off-by: Alex Shatov <alexs@att.com>
2018-01-24unit tests coverage 68% and more info in auditAlex Shatov6-106/+724
* refactored the unit test - simpler dh server initialization * new unit tests for the dcae-deployments * new unit tests for healthcheck - info * new server_instance_uuid - unique per deployment-handler instance for logging and info * dragging req object over the stack to show req data in logging and audit and metrics * new feature variable collection of policies per component in DCAE Change-Id: I8388d7e5e11e3a6c871cf3d507bd8a07b09add29 Issue-ID: DCAEGEN2-249 Signed-off-by: Alex Shatov <alexs@att.com>
2018-01-16variable collection of policies per componentAlex Shatov1-1/+1
* new feature variable collection of policies per component in DCAE Change-Id: Iafe366edd749220b347d1ba6f530d54c95e2f1a7 Issue-ID: DCAEGEN2-249 Signed-off-by: Alex Shatov <alexs@att.com>
2017-09-284.2.2. fixed starting up of deployment-handlerAlex Shatov1-2/+5
* start of dh was broken by coding for unit-test * Coverage summary Statements : 50.84% ( 514/1011 ) Branches : 26.11% ( 100/383 ) Functions : 30.11% ( 56/186 ) Lines : 51.35% ( 513/999 ) Change-Id: Ibb59f1ddd25a37a7bd58f4017837a622b04381e3 Issue-Id: DCAEGEN2-62 Signed-off-by: Alex Shatov <alexs@att.com>
2017-09-2751% unit test of the deployment-handlerAlex Shatov1-0/+221
* only unit testing the /policy/components at the moment * use -f Dockerfile_UT when building the image * unit test runs inside docker container * after docker run finishes copy the logs and coverage folder from docker container. Sample commands: docker cp test_deployment_handler:/opt/app/dh test_logs/ docker logs test_deployment_handler > \ test_logs/$(date +%Y_%m%d-%H%M%S)_test_deployment_handler.log 2>&1 Change-Id: I77276550e2ffb7094e02ffa20741afac6bfea96f Issue-Id: DCAEGEN2-62 Signed-off-by: Alex Shatov <alexs@att.com>