[
https://issues.apache.org/jira/browse/SLING-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Adamcin updated SLING-2419:
--------------------------------
Attachment:
madamcin_added_test_server_username_and_test_server_password_properties.patch
I added support for "test.server.username" and "test.server.password"
properties to the SlingTestBase and SlingRemoteTestRunner classes for
specifying a non-default set of credentials for server readiness checking and
for remote execution of sling junit tests. I also added constructor overloads
to several classes to accept a username and password as arguments, and added
getters to SlingTestBase to expose those values to integration tests for use in
other HTTP requests. Finally, for the sake of completeness, I updated the
sample integration test pom to demonstrate the use of these properties.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
