Developer guide for making Integration Tests

Overview

How to create folder and file in S3 bucket for prepare integrationTest

Integration Test Config for config of property in file resources.json, events.json and tests.json

Setup integrationtest

Create folder

• create folder in buckets s3

integrationtest-config-us-east-2/test_config/{your folder name}

• your folder name

1.Create name Developer for folder name inside test_config

2.Create folder service Names of Test

3.Create folder your test

integrationtest-config-us-east-2/test_config/{nameDeveloper}/{serviceNames}/{foldeTest}/

eg. integrationtest-config-us-east-2/test_config/mintDev/complexFilter/basicCase/

4.Can save file events, tests,resources inside

Note: can shared file events, tests,resources by bucket Prefix.

Create file

• files upload in s3'

-resources.json

-events.json

-tests.json

note ---------------------------------------------------------------------------------------------------------------------------

1.resources.json and events.json is json object

note :Can create these files in a SharedResource folder and share it with another test for collaborative usage

eg. integrationtest-config-us-east-2/test_config/jamesDev/SellOfferManager/SharedResource/resources.json

2.tests.json is json array of objects

• Detail of files

1.resources.json

• Syntax; resources Syntax

2.events.json

• Syntax; events Syntax
• If have many stage, Set initialStage is true only initial stage. Next stage not set this setting
• If snsSqsTrigger is true but not set snsServiceName or snsTopic
• If snsSqsTrigger and DirectSqs is false or not set --> direct invoke
• If DirectSqs and BatchSqsMessages is true --> direct invoke
• forStageMatching Use in test important parameter
• testValueMatches is default true

use case not test parameter random data eg. timeStamp or uuid

• If value in array or number or string is random. set testValueMatches: true and not set forStageMatching: true

Note ....

Multiple eventTags can be added to a single file events.json. but not same neme of eventTags

3.tests.json

• Syntax; tests Syntax
• Case test dynamodb (optional test) use dynamodbOutputEventIdentifiers in stage of test

• Upload file to s3

1. batchscript

2. upload to S3 bucket directly

#!/bin/bash 
set -u 

localPath="/home/dogsrcute/Programming mint/Fixed_Integrationtest/PluemDev/paginate/2stages" 
bucketName=s3://integrationtest-config-us-east-2/test_config/mintDev/fixed/PluemDev/2stages/ 

aws s3 cp "$localPath" "$bucketName" --recursive

• localPath is part to files for upload
• bucketName is your bucket

Type of parameter

Parameter type for create property in events.json

object: { 
	forStageMatching: true, 
	properties: {} 
}, 
array: { 
	forStageMatching: true, 
	eventValue: [] 
}, 
number: { 
	forStageMatching: true, 
	value: 1111 
}, 
string: { 
	forStageMatching: true, 
	value: "hi" 
}, 
boolean: { 
	forStageMatching: true, 
	value: true 
} 

// Case empty 
EmptyString:{ 
	value: "" 
}, 
EmptyArray:{ 
	forStageMatching: true, 
	eventValue: [] 
}, 
EmptyObject:{ 
	forStageMatching: true, 
	value: {} 
}

Test

1. create params for invoke IntTestingTestInitiateIntegrationTestHdrInv function

   { 
   	"serviceName": "ComplexFilter",  
   	"resourceType": "Lambda",  
   	"resourceName": "ProcessComplexFilterHdrSqs",  
   	"integrationTestTags": [ 
   		"test_S3_ByDev"  
   	],  
   	"bucketName": "integrationtest-config-us-east-2",  
   	"bucketPrefix":[  
   		"test_config/mintDev/basicCase/", 
   		"test_config/mintDev/SharedResource/"  
   	]  
   }
   

2. Find results in IntTestingTestTestRecord table

Working documents

Working_documents - Developer guide for making Integration Tests