Hi Waruna, In UI we first call host object isContextExist method and then validate it before add API. That is why you dont get this error in UI. AFAIR there is no rest API to check context existence. Its API developers responsibility to check this first. But still we need to have same check in add API method as well. So we might need to add this check in add API method(to work rest call properly).
Thanks, sanjeewa. On Wed, Sep 10, 2014 at 2:11 AM, Waruna Perera <[email protected]> wrote: > Hi, > > Issue logged in JIRA related to automation test case. > > [1] https://wso2.org/jira/browse/APIMANAGER-2835 > > On Thu, Sep 4, 2014 at 11:02 AM, Waruna Perera <[email protected]> wrote: > >> Hi Sanjeewa, >> >> Noted. I will update the thread as we move forward about the API calls >> which we will think of useful to have. >> >> Thanks >> >> >> On Thu, Sep 4, 2014 at 10:47 AM, Sanjeewa Malalgoda <[email protected]> >> wrote: >> >>> Hi Waruna, >>> >>> >>> On Wed, Sep 3, 2014 at 9:49 PM, Waruna Perera <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Amalka and me started doing above $subject by following[1]. When >>>> following some of the test cases available we found that API calls in >>>> publisher[2] and store are limited. The search API functions are covered by >>>> calling host objects. I have few questions regarding that. >>>> >>>> Do we have a plan to provide other API calls in publisher and store? >>>> >>> I assume here you are talking about rest APIs that we documented. For >>> the moment most of required operations are exposed as rest APIs. But still >>> there are missing parts. In such cases we can deploy simple jag file in >>> the server and call to host object. If you looked at HostObjectTestCase, >>> you will see how we tested host object operations that did not exposed as >>> rest APIs. Please refer java test cases available in product. >>> >>> Do we need uniformity with test cases? (some via API calls and others >>>> with direct host object calls) >>>> >>> IMO there is no such requirement. We cant test all scenarios in the same >>> way. Important thing is cover use cases as much as possible. >>> >>> Thanks, >>> sanjeewa. >>> >>>> >>>> [1] >>>> https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AmcQWA48EWBddEdzVVZ4aDJTVTBOeV9fVkE0dU9KMWc&usp >>>> >>>> [2] https://docs.wso2.com/display/AM170/Publisher+APIs >>>> >>>> -- >>>> Waruna Perera >>>> Senior Software Engineer - Test Automation >>>> Mobile: +94 77 3867037 >>>> WSO2, Inc.; http://wso2.com/ >>>> lean . enterprise . middlewear. >>>> >>> >>> >>> >>> -- >>> >>> *Sanjeewa Malalgoda* >>> WSO2 Inc. >>> Mobile : +94713068779 >>> >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :http://sanjeewamalalgoda.blogspot.com/ >>> <http://sanjeewamalalgoda.blogspot.com/> >>> >>> >>> >> >> >> -- >> Waruna Perera >> Senior Software Engineer - Test Automation >> Mobile: +94 77 3867037 >> WSO2, Inc.; http://wso2.com/ >> lean . enterprise . middlewear. >> > > > > -- > Waruna Perera > Senior Software Engineer - Test Automation > Mobile: +94 77 3867037 > WSO2, Inc.; http://wso2.com/ > lean . enterprise . middlewear. > -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
