Demo enhancements

[GoogleCodeExporter]

The demo is old and it shows. We need to:

1) Convert it to plain text format
2) Remove duplicate tests that only demonstrate the different abstraction
levels - in this demo we only need on workflow test
3) Write very detailed README explaining how to run tests using the
'rundemo.py' but also explaining how to start the demo app and Selenium
server manually.

Original issue reported on code.google.com by pekka.klarck on 27 Mar 2010 at 11:55

[GoogleCodeExporter]

Please provide some simple working examples that newbies can refer to or even 
just
try to copy. For me that's the best way to learn.

Original comment by lisa.cri...@gmail.com on 28 Mar 2010 at 12:12

[GoogleCodeExporter]

I have converted the test to plain text format and at the same time simplified 
and
cleaned up them and added some suite/resource documentation. The tests are 
visible in
Subversion [1]. I haven't created new zip package yet, but it's possible to 
checkout
[2] the demo if you are interested. I'm still going to update the README [3] 
and the
wiki page [4].

[1]
http://code.google.com/p/robotframework-seleniumlibrary/source/browse/trunk/demo
/#demo/login_tests
[2] http://code.google.com/p/robotframework-seleniumlibrary/source/checkout
[3]
http://code.google.com/p/robotframework-seleniumlibrary/source/browse/trunk/demo
/README.txt
[4] http://code.google.com/p/robotframework-seleniumlibrary/wiki/Demo

All kind of comments and improvement ideas related to the tests are highly
appreciated. There are also some issues I would like a second opinion:

1) In how detailed level should the test cases themselves be documented? Are the
current suite/resource docs fine if I add links to more information to the 
README?

2) Should the test have tags? They used to but I removed them to make tests as 
simple
as possible.

Original comment by pekka.klarck on 31 Mar 2010 at 12:26

• Changed state: Started

[GoogleCodeExporter]

I have finally updated the [Demo] wiki page and also created new download 
(available
on download page and linked from the wiki page). Comments are highly 
appreciated. I
can easily fix/enhance the documentation and creating new download isn't that
complicated either.

I have also cleaned up and simplified the `rundemo.py` script. Lisa, could you 
try
downloading the new demo and testing do you still get the error when Selenium 
Server
is shut down? Could you paste the stacktrace here if the error still occurs?

Original comment by pekka.klarck on 28 Apr 2010 at 1:01

[GoogleCodeExporter]

As far as I can see, this is the only bug standing in the way of the 2.3.2 
release :)
(if we're not taking in something else that has been reported in the meantime). 
What
is still left to do here, Pekka?

Andreas

Original comment by Andreas.EbbertKarroum@gmail.com on 14 May 2010 at 8:11

[GoogleCodeExporter]

I've been planning to add some troubleshooting instructions for the demo or,
preferably, for the library in general. This isn't actually related to the 
release,
though.

Original comment by pekka.klarck on 14 May 2010 at 2:58

• Removed labels: Target-2.3.2

[GoogleCodeExporter]

I'm pretty happy with the demo as it is now. Trouble shooting section for the 
library itself should/could be written, but that's not so much related to this 
issue.

Original comment by pekka.klarck on 22 Jun 2010 at 11:21

• Changed state: Done