Hi Irham,

in APIMANAGER3272ExternalLogoutPageTestCase, We have to give a custom
logout page url. I put it in the comment.

Thanks

On Wed, Apr 22, 2015 at 1:16 PM, Saneth Dharmakeerthi <sane...@wso2.com>
wrote:

> Hi Irham,
>
> About YouTubeUIPagesTestCase failure,
>
> Check whether *apiAccessInfo.getAccessToken() *passing the correct access
> token.
>  If the access token is different or empty, check the logic inside  
> doSubscribe()
> method in  org.wso2.am.integration.ui.tests.pages.store.StoreHomePage.java
> class.
>
> testAPIPage.testAPI(apiAccessInfo.getAccessURL() + API_METHOD, 
> *apiAccessInfo.getAccessToken()*);
> //Test response body
> assertTrue(testAPIPage.getTestResponseBody().contains(RESPONSE_BODY_TEST_STRING),
>  RESPONSE_BODY_TEST_STRING + " should be in the respond body");
>
>
>
>
> Thanks and Best Regards,
>
> Saneth Dharmakeerthi
> Senior Software Engineer
> WSO2, Inc.
> Mobile: +94772325511
>
> On Wed, Apr 22, 2015 at 12:39 PM, Irham Iqbal <iq...@wso2.com> wrote:
>
>>
>> Hi,
>>
>> Currently I am fixing the following APIM UI integration tests failures.
>>
>> Results :
>>
>> Tests run: 26, Failures: 9, Errors: 0, Skipped: 1
>>
>> When i go through the code i found the following lines which may causing
>> the test failures.
>>
>> APIMANAGER3272ExternalLogoutPageTestCase
>>
>>
>>    - Getting an 404 when try to access
>>    https://localhost:9443/store/site/pages/login.jag.
>>    - In the code variable externalLogoutPage has assigned "custom logout
>>    page url".
>>
>>
>> APIMANAGER3344ScopeSpecificTokenTestCase
>>
>>
>>    - Searching Select Scopes link inside My Subscriptions page in the
>>    store but i don't see any select scope link in that page.
>>
>>
>> APIMANAGER3363StoreAPIConsoleWithReverseProxy
>>
>>
>>    - When click on API Console tag getting an exception in log and also
>>    bellowing exception under that tag - 500 : undefined
>>    
>> https://localhost:9443/store/api-docs/admin%40apimanager3363.com/APIMANAGER3363/1.0.0
>>    .
>>
>>
>> APIMANAGER3366MultipleGatewayPublishTestCase
>>
>>    - In the publisher when adding the API in the manage state it's
>>    expecting input.env css selector  but it's not in that page.
>>
>>
>> APIMANAGER3371BusinessInformationClearedWhenAPISavedButton
>>
>>    - In the publisher when adding the API in the manage state it's try
>>    to click on xpath //form[@id='manage_form']/fieldset[3]/legend  but
>>    it's not in that page.
>>
>>
>> APIMANAGER3412DifferentRegistryContextPath
>>
>>
>>    - In the publisher when adding the API in the design state it's try
>>    to find a element by id jsonform-0-elt-production_endpoints but it's
>>    not in that page.
>>
>>
>> APIVersoinStatTestCase
>>
>>
>>    - In the publisher in the all API page when it's empty it's trying to
>>    find versionTxt by id but it's not in that page.
>>
>>
>> TestNameLengthTestCase
>>
>>
>>    - When running this test alone it's working. Some other test/tests
>>    might be the reason of failure of this test case.
>>
>>
>> YouTubeUIPagesTestCase
>>
>>    - testAPIPage.getTestResponseBody() gives <ams:fault xmlns:ams="
>>    
>> http://wso2.org/apimanager/security";><ams:code>900902</ams:code><ams:message>Missing
>>    Credentials</ams:message><ams:description>Required OAuth credentials not
>>    provided. Make sure your API invocation call has a header: "Authorization:
>>    Bearer ACCESS_TOKEN"</ams:description></ams:fault>
>>
>> Thanks,
>> Iqbal
>> --
>> Irham Iqbal
>> Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>> phone: +94 777888452
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0711241005*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to