Hi all,

The structure is as follows,

1. You need to add a publisher ( logger) to the respective alert stream
that you are testing
2. Delete the data in the respective data tables ( optional)
3. Do the publishing of simulation data ( either using a csv or
programmatically.
4. Run the spark scripts ( that are already deployed through the CApp)
5. Publish single/multiple events per test
6. Observe the logs for the alerts and assert them.

All these are supported by the framework.
ex: Observing logs : would returns the value of contains on a given assert
string
deleting data, running scripts, adding publishers, csv simulation ...etc

Since all the artifacts are deployed through the CApp at server startup, we
don't have to re-deploy them.

Thanks,
Sachith

On Wed, Mar 23, 2016 at 11:57 AM, Nirmal Fernando <nir...@wso2.com> wrote:

> Sachith has implemented the basic structure.
>
> @Sachith could you please send the latest details?
>
> On Thu, Feb 25, 2016 at 11:26 AM, Srinath Perera <srin...@wso2.com> wrote:
>
>> +1, when we have the first version, lets review!!
>>
>> --Srianth
>>
>> On Wed, Feb 24, 2016 at 5:19 PM, Sriskandarajah Suhothayan <s...@wso2.com
>> > wrote:
>>
>>> +1 looks good, for testing prepuces we can also deploy some related
>>> executionplans, stream and publishers to tap intermediate analytics
>>> results.
>>>
>>> Regards
>>> Suho
>>>
>>> On Wed, Feb 24, 2016 at 1:44 PM, Sachith Withana <sach...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We are going to implement the integration tests to cover the alerting
>>>> scripts being implemented in the process of developing Analytics for APIM.
>>>>
>>>> The integration test would be run against the DAS distribution for APIM
>>>> which would contain all the artifacts related to the APIM analytics such as
>>>> execution plans, streams ...etc.
>>>>
>>>> We will be using an APIM data dump ( generated using JMeter) to
>>>> initially populate the streams (using CSVs to simulate the data).
>>>>
>>>> Then for each script test, custom JMeter events would be published to
>>>> test the test scenarios and the output would be observed by listening to
>>>> the Alert Stream.
>>>>
>>>> FYI: currently we are planning to publish all the APIM analytics alerts
>>>> to a single stream, which would be observed by all the tests.
>>>>
>>>> WDYT?
>>>>
>>>> Thanks,
>>>> Sachith
>>>> --
>>>> Sachith Withana
>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>> E-mail: sachith AT wso2.com
>>>> M: +94715518127
>>>> Linked-In: <http://goog_416592669>
>>>> https://lk.linkedin.com/in/sachithwithana
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>>> *WSO2 Inc. *http://wso2.com
>>> * <http://wso2.com/>*
>>> lean . enterprise . middleware
>>>
>>>
>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
>>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>>>
>>
>>
>>
>> --
>> ============================
>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
>> Site: http://people.apache.org/~hemapani/
>> Photos: http://www.flickr.com/photos/hemapani/
>> Phone: 0772360902
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: <http://goog_416592669>https://lk.linkedin.com/in/sachithwithana
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to