Hi All,
A little update on this.Until we get the dependency hierarchy we are
continuing feature level testing with user management and
carbon-multitenancy features on it.
Thanks,
Iqbal
On Tue, Nov 11, 2014 at 2:40 PM, Irham Iqbal iq...@wso2.com wrote:
Hi All,
When i was installing the
Hi All,
As we discussed in the meeting,i tried the bellowing steps to prepare test
environments without other feature dependencies - e.g populate tenants into
DB using scripts rather using multi tenanted features.
1. Download the carbon-core and installed the user management and
Hi All,
When i was installing the carbon-multitenancy features i had to install the
following two features as well.
Because, carbon-multitenancy feature
org.wso2.carbon.tenant.common.server.feature.group requires both features.
feature
idorg.wso2.carbon.registry.core.feature.group/id
With this approach you are writing something in between unit and
integration but more towards integration tests. We can't describe feature
level automated tests as pure integration tests as other required
components to make it a product are not present. May be we need to come up
with new term for
Hi,
Will we be writing integration tests or unit tests with this approach? If
we are writing integration tests here, then we will have integration tests
in carbon component/feature repos in addition to what we already have in
product repos.
It's important to have automation tests at product
Hi all,
I am working on creating an environment to write test cases to test
standalone features. With new GIT module components and features should be
released prior to product releases, so all features must be thoroughly
tested and should be production ready. Carbon runtime is needed to test the
