In modern cloud services environments software components tend to be consumed in a variety of different ways:
- static library
- packaged static component
- as a service
accordingly, the testing associated with components would have to cover all of above, albiet the underlying functionality might be the same.
Izy platform recommends adhering to the izy-proxy JSONIO signature for implementing each test component. The advantages would be as follows:
- Ability to launch the test code from service and non service environments
- No need to manage the HTTP metadata and headers
- JSONIO api security context would be inhertied from the parent context, thus making passing authorization and authentization tokens free in the service environments.
- The component would become consumable anywhere in the environment by referecing izy-proxy
- simple string based launch patterns
//service/pkg:path?method could be used to reference the component call, making the component launch similar from
* command line shell and scripting environments
* browser sandbox
Framework agnostic test logic
Implement the core logic for the test and component by adhering to the JSONIO signature
. This will ensure that the tests can be consumed and deployed in the scenarios discussed above.
tie-in test compoments into the test framework
Use tools like test proxy
to properly launch and tie in the tests in the test framework.
Continious Integration (optional)
Enterprise customers can use continous cloud testing by using the Izyware dashboard advanced features. Please contact us for more information regarding using this feature.
test proxy: https://github.com/izyware/izy-proxy