You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Mark Adamcin (JIRA)" <ji...@apache.org> on 2013/02/16 01:17:12 UTC
[jira] [Commented] (SLING-2419) SlingTestBase,
SlingRemoteTestRunner, and SlingRemoteExecutionRule should support the
ability to use non-default credentials
[ https://issues.apache.org/jira/browse/SLING-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579621#comment-13579621 ]
Mark Adamcin commented on SLING-2419:
-------------------------------------
Thanks, Bertrand! I just built the testing bundles from the trunk, replaced my locally patched versions of them in an existing project with the trunk versions, and ran the integration tests once as admin:admin (succeeds), once as admin:shouldfail (fails), and once as a non-admin user (succeeds). Everything works as expected.
Any chance of a 1.0.8 release soon?
> SlingTestBase, SlingRemoteTestRunner, and SlingRemoteExecutionRule should support the ability to use non-default credentials
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-2419
> URL: https://issues.apache.org/jira/browse/SLING-2419
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: JUnit Remote Tests Runners 1.0.6, Sample Integration Tests 1.0.6, org.apache.sling.testing.tools 1.0.4
> Environment: Windows 7 64bit, Maven 3.0.3, Adobe CQ 5.4
> Reporter: Mark Adamcin
> Priority: Minor
> Fix For: JUnit Remote Tests Runners 1.0.8, Sample Integration Tests 1.0.8, org.apache.sling.testing.tools 1.0.6
>
> Attachments: madamcin_added_test_server_username_and_test_server_password_properties.patch
>
>
> For those who have gotten to the point of using the sling junit framework on an IT administered CQ5 development server, the fact that default admin credentials are hardcoded throughout the testing modules will present an inconvenient problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira