[
https://issues.apache.org/jira/browse/CAMEL-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168627#comment-15168627
]
Dhiraj Bokde commented on CAMEL-9363:
-------------------------------------
Integration tests for the component can be run using the profile
{{linkedin-test}} as follows:
{code}
mvn -Plinkedin-test
{code}
The user must provide credentials in
{{camel-linkedin-api/src/test/resources/test-options.properties}} and
{{camel-linkedin-component/src/test/resources/test-options.properties}} files
for running tests for the api and component modules. Note that the files use
the following default LinkedIn scopes:
{code}
scope=r_basicprofile,r_fullprofile,r_emailaddress,r_network,r_contactinfo,rw_nus,rw_company_admin,rw_groups,w_messages
{code}
For testing unverified LinkedIn applications, the scope should be changed to
the following default permissions. Some integration tests may have to be marked
{{@Ignored}}.
{code}
scope=r_basicprofile,r_emailaddress,rw_company_admin,w_share
{code}
Providing public LinkedIn account credentials is a security and operations
risk, since anyone could modify such an account and break integration tests.
> Provide camel-linkedin integration test
> ---------------------------------------
>
> Key: CAMEL-9363
> URL: https://issues.apache.org/jira/browse/CAMEL-9363
> Project: Camel
> Issue Type: Test
> Reporter: Thomas Diesler
> Assignee: Dhiraj Bokde
> Priority: Minor
>
> Please provide basic camel-linkedin integration testing.
> Perhaps a linkedin server can locally be stubbed or an actual connection to a
> remote server must be made. This can be driven by a maven profile that is
> activated when external security credentials are provided.
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/673
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
