Hi,
Webdav : after adding resources we can access them via Webdav but not the
other way around. This issue is already reported and we will be fixing it
on 5.0.0 [1].
Ws-i .net integration: I couldn't run related sample due to environment
issue. @Senaka, as we discussed could you please follow on
Completed smoke testing for Registry multi-profiles, APIM integration with
GReg and Basic Registry mounting.
Thanks
On Thu, Aug 29, 2013 at 9:12 PM, Lasith Chandrasekara las...@wso2.comwrote:
Hi,
Webdav : after adding resources we can access them via Webdav but not the
other way around.
Completed smoke tests for Multi tenancy, Scheduled tasks, Resource
versioning with RC4 pack
Regards,
Pulasthi
On Thu, Aug 29, 2013 at 11:07 PM, Shelan Perera she...@wso2.com wrote:
Completed smoke testing for Registry multi-profiles, APIM integration with
GReg and Basic Registry mounting.
Completed Life cycle , Subscription and notification related tests and
executed life cycle related integration test for user and tenant.
Regards,
Chandana
On Aug 29, 2013 11:23 PM, Pulasthi Supun pulas...@wso2.com wrote:
Completed smoke tests for Multi tenancy, Scheduled tasks, Resource
Testing done with developer studio IDE:
Resource browser - uploading txt and wsdl files
Create Registry Filter project - adding it as a dependency of a carbon
project
Create Registry Resources project - adding a resource from file system
But creating Resources Handler project caused the IDE to
Hi Isuruwan,
Please check with the Dev studio guys who sits right next to us.
thanks
Eranda
On Fri, Aug 30, 2013 at 10:26 AM, Isuruwan Herath isuru...@wso2.com wrote:
Testing done with developer studio IDE:
Resource browser - uploading txt and wsdl files
Create Registry Filter project -
Following are the areas that i have found to test please mention if you are
planning to do more. Do not try to repeat what has been covered by
integration tests.
1) Chandana - Life cycle related activities ( admin , non admin, new
lifecycle etc.) , Version and copy executors etc. (Can you run