After a year of moving the project to GitHub, changing jobs, moving to San Francisco and 4 beta releases, Windmill 1.4 is finally up on PYPI.
You may be asking, what in this release could be so awesome that it took a whole year+.. well the answer is, LOTS.
The major things that come to mind involve, automatically waiting for actions, dropping your unnecessary failure cases running in CI. We have also had major contributions to the Django integration code, the addition of Google Chrome on three platforms, and insane amounts of bug fixes you should checkout here.
Having delayed an insane amount of time in getting this out, I have to apologize that I haven’t had a chance to tackle the Win 7 Safari and Chrome issues, but they are next on the list (would love a contributions on this one).
I have really enjoyed working with all of you out there in the community, thanks for your continuing participation and the last year of patience!
That’s right! Open Source BBQ this Friday 4/9/2010 in Oakland, CA in my backyard at 4pm until it gets dark.
There will be meat, and stuff that’s not meat, and beer. Contributions welcome, it’s open source after all.
Everyone that writes code is welcome. Please RSVP at http://www.mobaganda.com/opensourcebbq.
I live walking distance from MacAurthur BART, here is a map. When you get there just walk down the driveway in to the backyard.
Friday is also “open friday” at the couch.io office so you can come and work/play at the office during the day and then roll up to the BBQ around 4 if you like.
Disclaimer: Image is for effect only, hot rod BBQ will not be attending.
I’ll be leaving tomorrow morning for [Open Source Bridge](http://opensourcebridge.org/) in Portland, Oregon.
I’m putting together a new [Windmill talk](http://opensourcebridge.org/sessions/36) that tries to incorporate all the feedback we’ve received over the last year of speaking which I’ll be presenting on Thursday.
Mozilla is also a [sponsoring](http://opensourcebridge.org/sponsors/) the conference and there is going to be some great [Firefox related sprints in the hacker lounge](http://opensourcebridge.org/wiki/Hacker_Lounge). Dietrich is also giving what sounds like an awesome talk on extending Firefox called [Firefox Switchblade](http://opensourcebridge.org/sessions/251).
Hope to see you all there!
PS. I’ll also be at EuroPython and the Community Leadership Summit, more on those later
Getting back in the swing of things after conferencing for weeks can be pretty painful, thus the lateness of the post. However I think it’s important to go over some thoughts still lingering in my brain as a result.
First off, I have to say that for those of you who don’t know, PyCon is a community organized event, and amazingly well done. I was impressed by the design of the conference, the way they had four talks going on at once and they tried to keep them in a similar interest track. Every talk I attended was at least “good”, and many were “great”. You could really feel a community vibe, and for a conference that had 800+ attendees in the middle of a major recession they had every right to be excited.
There were two major themes content wise that really impressed me, the first was an amazing amount of web framework focus. Django obviously being the twinkle in the eye of the community, but there were smaller communities for each of the other projects, Pylons-Turbo Gears, web2py and lots of tools built on top of them. One that struck me with some major promise is the Pinax Project. Their goal is to make it so that I don’t ever have to deal with building user registration and in site messaging… and all the other features expected for any site that has social network functionality.
The other major theme was a mini testing conference going on within PyCon, that I was very comfortable hanging around with. We had a hugely successful Birds Of a Feather, as well as a surprisingly active Open Space talk for Windmill.
The “Using Windmill” talk turns out to be pretty successful in every aspect that I really care about. I do wish that I had been able to get a little more sleep the night before, and I have to admit the size of the venue was a bit overwhelming. I now realize watching the footage that I used the word “UM” way too much, and the demo videos must have been hard to watch from the very back of the room. But barring those two things, I am quite happy (I shall learn and practice for the next round of shameless PR at OSCON 2009).
The “Functional Testing Tools in Python” panel was very successful, and a lot of fun. I always enjoy the friendly banter between the different project owners. Everyone has a different opinion on what they care about, focus on and feel they do the best. Obviously since the only two projects represented that focused on Web Testing were Windmill and Selenium, we got a lot of attention.
Watching that panel footage I definitely think that the introductions were too long, but I still think our Journey themed – mind blowing – Windmill demo video was a great intro. At the very least, the audience had a little entertainment before the geek droning began
Slide had an awesome presence this year, a fun booth, huge banners everywhere and 6 attendees. It was fun to see all of the great responses I received about Slide from people out there in Python land.
Here are links to the videos:
- Using Windmill: http://pycon.blip.tv/file/1947236/
- Functional Testing Tools in Python Panel: http://pycon.blip.tv/file/1947342/
And some pictures:
Today Windmill 1.0RC1 was finally pushed to the pypi!
We advise that you:
easy_install -U windmill
This release includes an absolutely huge list of bug fixes, including some very important issues in the proxy server and drag and drop code. The list of bugs fixed can be found in the 1.0 section on the Trac Milestone.
At this point we are looking for critical blockers only for the 1.0 release, which we are planning to push before PyCon US next month. Please log any issues you find in Trac so that they can be triaged accordingly.
As some of you may know, we have recently moved our hosting over to OpenQA, we are very excited to join that community and the great projects it represents. In addition to the great tools we are using we now have even more available to us, including the OpenQA instance of FishEye.
Thanks for your continued interest, contributions and involvement — as always we are available in #windmill on freenode!
We are another step closer to 1.0, if you have been watching the mailing lists or the trac timeline you already know that we have had some serious bug fixes over the past couple weeks as well as one new feature.
- Major fixes and updates for the Windmill Unit Tests
- IE fixes for: Drag and Drop, Click, UI usability, Non Compress deps broken
- JS Test Framework bug fixes, JUM assertions, unit tests,
- Improved XPath Generation and bug fixes
- Full support for launching and killing Google Chrome on Windows (requires Python 2.6)
We really appreciate all the bug reports and emails from you all, thanks for your patience as we try to squash all the bugs.
An additional encouraging note is that we got some great PR this week, which can be found here: Windmill Article in the SDTimes.
Another round of productive bug fixes and feature additions have happened over the last few weeks. We are now positioning the project to approach a 1.0 release, which means that our goals for the coming releases is focused on shaking out all those blocker bugs before we push the big milestone.
New Features, since 0.8.0
- Command line option for changing service port
- Django Support
- Forwarding Conditionals
- Addition of firebug lite support in IDE and Testing Application
- Fully functional wxWindmill contrib application
- Enhanced ’smart’ recorder
- Auto element scroll into view to more closely simulate users
- Improved IDE user interface
- Improved frame recursive element look ups for IE
In addition to all the bug fixes, which you can see for yourself in trac.
We are really excited to see the exponential growth and exposure the project has been getting over the past couple weeks, thanks everyone!
I have spent nearly every day since July 7th working to bring the Windmill Project up to a level where it can be used reliably in a production environment. Our mission starts with “Windmill is a web testing framework intended for complete automation of user interface testing”, of course this refers to the web including everything and anything inside the browser window. This turns out to be a very large task, one that only an Open Source labor of love could possibly attempt to accomplish.
Windmill has slowly evolved as a project with user contributions, a moderately active IRC channel, and enough users to keep me from forgetting what a useful and powerful tool it is. When I was offered the opportunity to work on the project I quickly saw how much needed to be done in order to get to where we needed to be. We still aren’t quite there, and like most Open Source projects we might not ever get to the envisioned perfection, however recently we hit a very important milestone. The project is now fully hosted and run by the committers, and in many ways “Grown Up”, thanks to a lot of good advise and hard work. The milestone we have reached, is that Windmill is ready for YOU to use. This week we pushed 0.8.2, which is a release that has addressed all of the major issues that we know about and have discovered with heavy usage over the past months. Our hopes are that you will go install Windmill 0.8.2 and things will just WORK. If not, I can’t wait to get your issues in trac and see what we can do to fix them.
The main things we care about when it comes to our web testing tools:
- Low barrier to entry, low learning curve, and ease of use
- Thorough documentation, community and project support
- Support for the big 3 platforms; Windows, MacOSX and Linux
- Support for the big 4 browsers; Firefox, IE, Safari and Opera
- Easy integration with continuous integration tools
- Reliability; developers aren’t going to pay attention if the failures aren’t real
- A really nice looking logo, and a web site that is easy on the eyes..
There are always more features to implement, but Windmill hasn’t needed new features for a very long time. What Windmill needed was some serious QA, some code cleanup and a whole mess of bug fixes. If you look through the Trac Timeline you will see the massive amounts of all of the above that have happened and I am proud as hell when I launch the application today and see all that it can do.
What can Windmill do?
Windmill offers the ability to build, write, record and run tests as well as aid in debugging and development. In addition, the framework provides the ability to create and maintain hierarchies of smart and thorough tests that will ensure the quality of your web applications over time. Not only can we save you hours creating and maintaing tests, but we can also help you see your web application as a growing feature rich product, instead of a QA nightmare.
Many tools out there provide ways to write tests, some even provide recorders and DOM explorers, but none that I have ever seen provide this rich functionality cross platform and cross browser, which is really what is required in order to build a thorough test repository that represents all your possible users.
Keeping it Open
One of the most exciting things to me personally about this particular project is the immense potential user base out there, and the large impact the Windmill Tools can have on the daily work flow of it’s users. Windmill was obviously inspired with the hopes of minimizing the need for manual testing of rich web applications, and has grown to be much more than that.
The future of the work to be done on Windmill will primarily be driven by the needs of it’s users, the changes and development of the industry and the success of it reaching the goal, to make web automation better.
Concluding this major push of work, testing, documentation and moving of infrastructure; we now need to see how the community feels. There are lots of choices out there for web automation and we have made many differentiating choices along the way. It is now time to get the word out and take in some real feedback.
Thanks you all for input, contributions, patience and valuable feedback. Those of you who spent many hours on Freenode in #windmill with us debugging and hunting down those spastic blockers are troopers and we really appreciate it.