Re: [DISCUSS] Enduser Test Profile

Hi Francesco, yes, that's what I would like to do, so the new user profile would override existing plugin configurations. I undestand that would be the right solution. Thank you. Matteo. On 21/11/2016 17:47, Francesco Chicchiriccò wrote: On 21/11/2016 17:37, Matteo Di Carlo wrote: Hi, here

Re: [DISCUSS] Enduser Test Profile

On 21/11/2016 17:37, Matteo Di Carlo wrote: Hi, here is one possible solution I found today to run tests AND prepare a test environment in the same time. Test related plugins are included in a new profile. This could be a good

Re: [DISCUSS] Enduser Test Profile

Hi, here is one possible solution I found today to run tests AND prepare a test environment in the same time. Test related plugins are included in a new profile. This could be a good solution if the new profile is the only one

Re: [DISCUSS] Enduser Test Profile

Matteo, please draft an updated fit/enduser-reference/pom.xml somewhere (gist, as suggested should be good enough) so that we can take an effective look at the proposed changes. Thanks. Regards. On 18/11/2016 18:03, Andrea Patricelli wrote: Hi all, I think that hacking the pom.xml of the

Re: [DISCUSS] Enduser Test Profile

Hi all, I think that hacking the pom.xml of the fit/enduser cannot be a long lasting solution. So I agree about introducing a specific profile for developing of IT tests, it could help for the current developing needs. It would also be cool to have more granularity and run specific tests using

Re: [DISCUSS] Enduser Test Profile

On 18/11/2016 16:00, Francesco Chicchiriccò wrote: On 18/11/2016 15:20, Matteo Di Carlo wrote: Hi all, I would like to share some considerations about enduser testing. After tests have been written or updated we are able to run them manually through node and protractor directly from

Re: [DISCUSS] Enduser Test Profile

On 18/11/2016 15:20, Matteo Di Carlo wrote: Hi all, I would like to share some considerations about enduser testing. After tests have been written or updated we are able to run them manually through node and protractor directly from ${enduser-test.dir}: a directory created in

[DISCUSS] Enduser Test Profile

Hi all, I would like to share some considerations about enduser testing. After tests have been written or updated we are able to run them manually through node and protractor directly from ${enduser-test.dir}: a directory created in /fit/enduser/target during pre-integration-test phase.