You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2017/11/29 22:36:47 UTC

[GitHub] pritidesai opened a new issue #658: Should Integration Tests run in Parallel or in Sequence?

pritidesai opened a new issue #658: Should Integration Tests run in Parallel or in Sequence?
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/658
 
 
   As part of fixing this issue, please make sure that we have all integration tests uncommented and back running without failures.
   
   Now, we have hit concurrency issue many times before with integration test and as I was talking to Matt, Matt suggested to document these following points:
   
   We have to create standards for writing integration test. There are different kinds of tests written so far:
   (1) an integration test with single manifest and single deployment file and running deployment and undeployment in a single test function.
   (2) an integration test with multiple manifest and multiple deployment files running deployment and undeployment in separate test functions (one for each) or running deployment and undeployment in a single test function.
   (3) an integration test with multiple manifest and multiple deployment file but having the same content, like, same package name, trigger name, rules etc.
   
   We have to decide which of these tests are acceptable keeping in mind the fact that the integration tests are running in parallel. Now, is it a valid use case that two different developers trying to deploy or undeploy the same application at the same time from two different machines. Based on this discussion and setting our expectation, please create standards on writing integration tests and document them. Also, discuss and decide whether all the integration tests should be running in parallel or in sequence (with setting `-p 1`).
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services