On Wed, Sep 22, 2010 at 11:18 AM, Hiranya Jayathilaka <[email protected]>wrote:
> > > On Tue, Sep 21, 2010 at 7:27 PM, [email protected] <[email protected]>wrote: > >> When running log mediator tests manually, we usually scan carbon log >> to read log messages and decide the success or failure of the tests . >> But how can this be done through admin service automated framework? >> Currently we have written a primitive method to capture log messages >> based on timestamp and then read the log message.But it seems to be a >> error-prone mechanism.can someone please provide us guidance with a >> better mechanism in reading logs while running automated tests? >> > > How about using the LogViewer admin service to retrieve the logs > programmatically? Anyway I don't think you can use timestamp values as a > basis of verification. You have to solely depend on the content of the log > messages. > will check it with LogViewer admin service. What we are currently doing for log mediator tests is, checking the contents of the log based on the timestamp (search whether the expected content has been written to the log on that particular time). > > Thanks, > Hiranya > > >> >> Thank you, >> Chamara/ >> -- >> Suminda Chamara Silva >> WSO2 Inc. >> Mobile: +94 718 302858 >> blog: http://chamaras.blogspot.com >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
