wet-announce Mailing List for WET
Status: Alpha
Brought to you by:
raghublr
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Raghu V. <ra...@qa...> - 2007-06-17 21:49:56
|
After 2+ weeks in alpha, full system testing and a lot of effort on documentation, Wet 1.0's beta was released on 17th June 2007. The plan is that it will be in beta for 4 weeks and after more testing + docs, will become GA. The following is the news that went out in the openqa site: WET 1.0 beta was released on the 17th of June 2007. This release is a major shift from the 0.9.8 release and packs a lot of goodies!! The release can be downloaded from: http://wet.qantom.org/downloads/Wet_1.0.0.beta.exe^ After the 1.0 alpha release, made on 26th May 2007, there have been a few additional bug fixes. For details about these issues, check the release notes which can be found at: http://wet.qantom.org/release_notes_1.0_beta.html^ An install guide is avaiable at: http://wet.qantom.org/InstallationGuide.html^ This version has a few documents which can be found at one of the following two places: 1. Openqa Wiki page 2. On the WET's main website - under the docs tab Apart from this, there is a quickstart guide http://wet.qantom.org/1.0/docs/QuickstartGuide.html^ which is a quick tutorial. Special thanks to ... I'd like to extend a hearty thanks to Shruthi and Saraswathi for their efforts in developing / testing 1.0 and Chitra for testing the release. Raghu |
From: Raghu V. <ra...@qa...> - 2007-05-26 10:55:05
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> 1.0 has been finally released as alpha. This release is behind schedule by around 2 months but this delay is due to two major changes -<br> <br> a) WET -171 (Create Dom Processing directly in C#) - To reduce the dependancy on the WET RPC which turned out to be a big source of errors. <br> <br> b) WET -308 (Disintegrate the WET UI) - This was created to change the way that WET was perceived to be! Somewhere, while creating the WET UI for 0.9.8, we screwed up and sent the wrong signals that WET was like a record-playback tool and will let you create test suites by simply recording user actions. Well WET was never meant to be that way right from its conception (See <a class="moz-txt-link-freetext" href="http://wet.qantom.org/wet_philosophy_mini.html">http://wet.qantom.org/wet_philosophy_mini.html</a> and the page that is linked to from there). To fix this perception, WET-308 was thought of - and it turned out that this implementation was a lot more time consuming than we initially thought!<br> <br> I would like to extend my heartfelt thanks to Shruthi J, Saraswathi and Chitra for their efforts in making the alpha release a reality. Thanks a lot folks!<br> <br> More information about this release can be seen at:<br> <br> <a class="moz-txt-link-freetext" href="http://wiki.openqa.org/display/WET/2007/05/26/Wet+1.0+alpha+released%21%21%21">http://wiki.openqa.org/display/WET/2007/05/26/Wet+1.0+alpha+released%21%21%21</a><br> <br> Please read the caveats section carefully before deciding if you want to plunge into using the release right away or wait till Beta is released. <br> <br> <div class="moz-signature">-- <br> <small>Regards, <br> Raghu Venkataramana<br> <img alt="" src="cid:par...@qa..."> <small>The future of web testing<br> </small> <a href="http://www.wet.qantom.org">www.wet.qantom.org</a> <br> </small></div> </body> </html> |
From: Raghu V. <ra...@qa...> - 2006-10-02 06:08:46
|
All, 0.9.8 final release of WET is now out. This release is behind schedule. As per the original plan, a 0.9.8 beta2 was supposed to have been released around the 1st of September. However there were two main improvements, which were not initially on the list, that were added to the 0.9.8beta2. These are: 1) WET-169 - Simulated browser should match the real browser as close as possible. 2) WET-107 - Use XML RPC as the method to communicate data between Ruby and VC# These issues were initially on the 1.0 list. However, since WET-169 was a cause for a big confusion among users and WET-107 was minimizing the communication failure between the ruby layer and C# layer, we decided to bite off the bullet and implement them for 0.9.8 itself. Finally, this release has gone through some extensive testing and has passed all the release criterea. Considering this fact, we also decided to skip beta2 and go directly with the final release. The build is at http://wet.qantom.org/downloads/wet_0.9.8_setup.exe After getting the build, please go through the documentation / website to ensure that you have all the information required. The various docs / links of interest are: 1) Release Notes - http://wet.qantom.org/rel_notes_0.9.8.html 2) Install Guide - http://wet.qantom.org/installguide.html 3) Quickstart tutorial - http://wet.qantom.org/quickstart_tut.html 4) Guide to using wet - http://wet.qantom.org/stepbystep.html 5) The complete WEB site - Yes! The whole of http://www.wet.qantom.org has been changed. Please report any issues to the forum/Jira. Regards Raghu Venkataramana -- Regards, Raghu Venkataramana /Director/ *Qantom Software Private Limited* 72/1B, 2nd Floor, K.H. Plaza, Kanakapura Road, Bangalore-78 Phone : 26655216, Telefax : 26799269 SQA partners for your products www.qantom.com <http://www.qantom.com> The future of test tools is open source www.wet.qantom.org <http://www.wet.qantom.org> |
From: Raghu V. <ra...@qa...> - 2006-04-15 21:52:12
|
All, Greetings!! For a little while there have not been any releases for WET. One of the main reasons for this is due to some organizational changes that we had here at Qantom - We moved to a bigger office and also were working out a strategic partnership with our associates, Thwameva Technologies. Thwameva will be investing a lot of effort in the future development of WET. I will write more in detail about that in a few days. First things first: After a long delay, WET 0.8 has now been released. Although there has been silence on the mailing list, it has not been so, in terms of development of WET itself. We have constantly been working on various aspects of WET. This release is a major jump from the first version of WET (0.5.1). There are quite a few enhancements and refinements that have been made in this version. A couple of important additions in this version, are a) the availability of a thorough set of documentation (In fact, the document alone delayed the release by over 45 days) and b) a windows installer. The details for the installer is available by navigating to http://wet.qantom.org/download.html. Thanks Raghu Venkataramana Below is the release notes for this version: ======================================================== RELEASE NOTES - WET 0.8.0 ======================================================== Version 0.8 is a big improvement over 0.5. For months, at Qantom, we have been constantly working on WET. In the process, we have fixed many bugs and added a variety of The features that have been introduced in 0.8 (w.r.t 0.5.1) are: 1) Much simpler installation of WET by the use of an installer file. The installer also installs Watir, if required. 2) A comprehensive set of documents are now available 3) Test definitions offer much more power. Test-definitions can now use either hard coded string literals or a ruby command which is evaluated at run time. 4) Preconditions and teardowns can now be defined as components of test definitions. The ability to do so allows your automated script to mimic a manual test more closely 5) Support for library test scripts - call_test, a new feature that has been added allows you to earmark certain tests as ibraries.These library tests can be called from other tests. 6) A test suite can be run by the use of the BatchRunner utility. This utility allows you to run multiple tests in the specified order. After running all the tests, the BatchRunner displays the result of running the entire test suite in a single WEB page. 7) Object repository parser is now a pure ruby(and opensource) implementation. Previously it was a win32 dll that was used by WET 8) Test results are much more informative especially in case of failed test steps. 9) Dependancy of MS Excel has now been removed for Datatable support. Datatables can either be an excel spreadsheet or an XML file. There are utilities to convert an Excel Datatable to XML Datatable and vice-versa. 10) Easier creation of WET scripts by virtue of an improved show_objects method. The show_objects method is customizable in terms of the parameters to be used for identifying objects at run-time 11) The implementation of the classes manipulating the browser's DOM objects has been abstracted from WET's test methods. This implementation adopts a factory based approach for accessing browser implementations. Although currently there is only browser implementation that is supported (which is Watir - Watir in turn is a IE browser tester), this technique will be very helpful when adding support for other browsers. When other browsers are added, it should be possible to completely reuse the same set of testscripts on those browsers. |
From: Raghu V. <ra...@qa...> - 2005-09-14 15:05:15
|
Hi all, A minor release of WET is out at the downloads area which can be reached at http://www.wet.qantom.org/download.html. This release addresses the following issues: 1) Rdoc now covers a lot more ground. This is one of the areas that Wet is really lagging behind. In this release, documentation has been added to the source and these can be seen in the rdoc for wet. There is still a lot more to do in terms of the documentation - but this is the first step . 2) Added the ability to define test definitions / global configuration parameters as either 'string literals' or 'ruby commands'. In case of the later - the command is evaluated. For example, you can set the repository file to either : repository.path = C:/all_repositories/myrep.xml or repository.path = eval #{ENV['QWT_HOME'}/myrep.xml 3) Test results is now configurable using the global definitions file. The test result file can either be a literal hardcoded file name or a ruby command to be evaluated. A typical use for this is to set the testresults file to a timestamp. Example: [Results] file=eval #{Time.now().strftime('%y%m%d_%H%M')}_results.html The global definition is found at : %QWT_HOME%\etc\global-config.cfg 4) Fixed a few bugs in the Checkpoints and the Textarea - Thanks Ian, for pointing these out. 5) Results' Save method was failing if the target directories didn't exist. Fixed it such that now all the parent level directories are first created. 6) Adding support for ability to run multiple iterations - This is required if we want to run the same test for each row of the datatable without having to specifically mention the 'category' of data. 7) Last and definitely not the least, there are now unit tests for most of the classes. The unit tests are not complete by all means but cover significant ground for those APIs that are Wet specific. Regards Raghu |