Hi Nuwan, I think #1 is good, some rough time is good enough IMO.
--Srinath On Thu, Mar 29, 2012 at 9:28 PM, Nuwan Wimalasekara <[email protected]> wrote: > Hi Srinath, > +1, > The problem is that time stamp fact can not find directly from reports > xml's. > so there are two options > 1). get the minimum execution time among the test suite execution time > 2). store time stamp when starting test frame work and use it as the time. > > need to find best one. > we will select one of above and add time stamp with build number. It is > also a important information. > > Thanks > Nuwanw > > > On Wed, Mar 28, 2012 at 1:13 PM, Srinath Perera <[email protected]> wrote: > >> Hi NuwanW, >> >> This looks great! Can we put the date with the build number as well? >> >> --Srinath >> >> On Tue, Mar 27, 2012 at 9:06 PM, Nuwan Wimalasekara <[email protected]> >> wrote: >> > Hi Srinath, >> > >> > You can access to the dashboard though following URL. Please note the >> link >> > is not accessible from outside. >> > >> > http://192.168.0.21:9770/dashboard-4.0.0-SNAPSHOT/index.jsp >> > >> > Thanks >> > Nuwanw >> > >> > >> > On Mon, Mar 26, 2012 at 3:35 PM, Krishantha Samaraweera >> > <[email protected]> wrote: >> >> >> >> Hi Srinath, >> >> >> >> We lost automation test plan from bamboo due recent bamboo clean up. >> Need >> >> to setup the framework again on bamboo and configure it. BTW, last >> time we >> >> configured the automation framework to run after a successful build. >> However >> >> the framework got executed only few times as the build was >> unsuccessful. I >> >> think this is high time for us to setup the framework again on bamboo >> >> machine, will work on it. As the first step, we will include AS, ESB, >> G-Reg, >> >> DSS and BPS tests. >> >> >> >> Will send a link to hosted Dhasboard instance shortly. >> >> >> >> Thanks, >> >> Krishantha. >> >> >> >> >> >> On Mon, Mar 26, 2012 at 2:45 PM, Srinath Perera <[email protected]> >> wrote: >> >>> >> >>> do we have this Dashboard deployed with our Bamboo automation tests? >> >>> if so, please send a link. >> >>> >> >>> --Srinath >> >>> >> >>> On Sat, Mar 17, 2012 at 7:54 PM, Amila Maha Arachchi <[email protected] >> > >> >>> wrote: >> >>> > Nice work! >> >>> > >> >>> > Regards, >> >>> > AmilaM. >> >>> > >> >>> > On Fri, Mar 16, 2012 at 4:28 PM, Nuwan Wimalasekara < >> [email protected]> >> >>> > wrote: >> >>> >> >> >>> >> Hi all, >> >>> >> >> >>> >> One of main drawback in System test framework was to keep test >> report >> >>> >> history in place where we can see test status and stats. System >> test >> >>> >> framework generate test reports as TestNG result XML files. But >> those >> >>> >> reports only show the result of last test run. So there is no way >> to >> >>> >> find >> >>> >> past results by build. Therefore we added new feature to System >> test >> >>> >> framework to parse result XML files and write result data to a >> >>> >> database >> >>> >> after each test framework execution. Dashboard is capable for >> display >> >>> >> those >> >>> >> result in proper manner. >> >>> >> >> >>> >> Dashboard address the visualization of the test results and history >> >>> >> using >> >>> >> Charts. Test Automation dashboard is a web application which >> display >> >>> >> test >> >>> >> results and history of System test framework builds. Web >> application >> >>> >> is >> >>> >> developed using JSP technology. It is bundled as a webapp file and >> can >> >>> >> be >> >>> >> deployed on any java application server such as WSO2 App server, >> >>> >> Tomcat >> >>> >> etc.. We have designed the Dashboard as separate project and >> >>> >> integrated to >> >>> >> System test framework. Related dashboard DB configuration can be >> found >> >>> >> in >> >>> >> framework.properties file in System test framework. So the idea is >> to >> >>> >> reuse >> >>> >> the Dashboard with any project which generate TestNG result XML >> files. >> >>> >> Automation dashboard source can be found at [1] >> >>> >> >> >>> >> How to deploy Dashboard : >> >>> >> >> >>> >> 1). Check out source of a dashboard from [1] >> >>> >> 2). Build the source to generate war file (mvn clean package) >> >>> >> 3). Extract a war file and open dbconf.properties in >> /WEB-INF/classes >> >>> >> directory. >> >>> >> 4). Configure database connection properties(jdbc url should be >> same >> >>> >> as >> >>> >> database configuration in framework.property) >> >>> >> 5). Deploy the war fine on a application server. >> >>> >> 6). Run System test framework and check results using dashboard >> >>> >> >> >>> >> It will display all test result and you can navigate result history >> >>> >> also. >> >>> >> >> >>> >> Please refer attached screen shots of Dashboard. DB script and >> table >> >>> >> structure is also attached. >> >>> >> >> >>> >> Your feedbacks and suggestions are welcome. >> >>> >> >> >>> >> Thanks Chanaka for the support given for theme design. >> >>> >> >> >>> >> Thanks, >> >>> >> NuwanW /Chamara >> >>> >> >> >>> >> >> >>> >> >> >>> >> [1] >> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/dashboard/ >> >>> >> -- >> >>> >> Nuwan Wimalasekara >> >>> >> Software Engineer - Test Automation >> >>> >> WSO2, Inc.: http://wso2.com >> >>> >> lean. enterprise. middleware >> >>> >> >> >>> >> phone: +94 71 668 4620 >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> _______________________________________________ >> >>> >> Dev mailing list >> >>> >> [email protected] >> >>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Amila Maharachchi >> >>> > Senior Software Engineer; WSO2, Inc.; http://wso2.com >> >>> > >> >>> > Blog: http://maharachchi.blogspot.com >> >>> > Mobile: +94719371446 >> >>> > >> >>> > >> >>> > >> >>> > _______________________________________________ >> >>> > Dev mailing list >> >>> > [email protected] >> >>> > http://wso2.org/cgi-bin/mailman/listinfo/dev >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> ============================ >> >>> Srinath Perera, Ph.D. >> >>> http://www.cs.indiana.edu/~hperera/ >> >>> http://srinathsview.blogspot.com/ >> >>> _______________________________________________ >> >>> Dev mailing list >> >>> [email protected] >> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> >> >> >> >> >> >> _______________________________________________ >> >> Dev mailing list >> >> [email protected] >> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> >> > >> > >> > >> > -- >> > Nuwan Wimalasekara >> > Software Engineer - Test Automation >> > WSO2, Inc.: http://wso2.com >> > lean. enterprise. middleware >> > >> > phone: +94 71 668 4620 >> > >> > >> > >> > >> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> Senior Software Architect, WSO2 Inc. >> Visiting Faculty, University of Moratuwa >> Member, Apache Software Foundation >> Research Scientist, Lanka Software Foundation >> Blog: http://srinathsview.blogspot.com/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> > > > > -- > Nuwan Wimalasekara > Software Engineer - Test Automation > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > phone: +94 71 668 4620 > > > > > -- ============================ Srinath Perera, Ph.D. http://www.cs.indiana.edu/~hperera/ http://srinathsview.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
