So here, from what I understood, what we are supposed deliver are below - a set of curl commands (since the block layer calls can be executed as REST calls) with validations whether they generate correct results - a shell script to execute all the above curl commands
With the CI/CD effort, we will be running integration tests daily. Generally, when the integration tests finishes, we wipe out the system. In this case, we will not flush any tenant data soon after integration tests end, and let this script run against this setup. Then, once these block layer tests are executed, we can wipe out the system. WDYT? Thanks Manisha On Wed, Apr 22, 2015 at 5:47 PM, Dimuthu Leelarathne <[email protected]> wrote: > Hi all, > > Here are some high level goals that comes to my mind. Please keep adding > to the list. > > 1 - Complete block layer covered. We are not looking at end-to-end user > story coverage. But complete block layer coverage. End to end user story > testing will be done by Selenium later > 2 - Tests must run in Staging, Public Cloud, Dev > 3 - All app types must be tested > > WDYT? What else should we cover? > > thanks, > dimuthu > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ <http://manisha-eleperuma.blogspot.com/>* *mobile: +94 71 8279777*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
