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
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
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
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.
[
https://issues.apache.org/jira/browse/SYNCOPE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Di Carlo resolved SYNCOPE-970.
-
Resolution: Fixed
> On logout, page translation doesn't reset to default settings.
>
[
https://issues.apache.org/jira/browse/SYNCOPE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676565#comment-15676565
]
ASF subversion and git services commented on SYNCOPE-970:
-
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676564#comment-15676564
]
ASF subversion and git services commented on SYNCOPE-970:
-
Commit
