what are the advantages to using Parasol for Selenium vs just using the JS client?

I'm trying to decide which one to start using for a project and can make arguments both ways.  


For the people who use Parasol, why did you choose it vs using another language client outside of the image?


Thanks

Paul_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Paul,

If you mean writing tests for your seaside/amber app in another language outside the image, then that’s the main reason I chose Parasol/Selenium :)

My tests are written using SUnit and in Smalltalk (just just the rest of my tests and code), are packaged and loaded with Metacello (just like the rest of the application) and worked in both Pharo and GemStone.

Although I’m sure this is true of other solutions, I like how easy it is with Parasol/Selenium to have the same tests run on Safari, Chrome, Firefox, iOS and Android with one click on the test runner.

For testing, if Selenium (and Parasol’s control of selenium) doesn’t limit the ability to interact with the browser over any other solution, then the clincher for me was keeping it all in one language, and one environment.

Cheers,

J

PS. Maybe it’s just that I’m a Smalltalk addict, however, if my project can keep external solutions and other languages to a minimum, (Smalltalk rather than SQL, HTML Javascript, JSON, XML an so on) then all the better - the front end developers can support back end developers can support the testing team, etc. since they can all read and understand each others code. The only thing missing from the Smalltalk stack is an integrated way of working with SASS and Seaside/Amber… but getting off track.

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Parasol gives you the ability to write complete end-to-end tests: simulate the actions of a user in the browser and verify the outcome on the Seaside backend.
This is because you have access to both the Seaside component state and, more importantly, the database used by your app, in the same environment where the test executes.

This means that:
- you can parameterize the tests with the database and the seaside state
- you can verify the outcome of the actions made in the web browser directly in the backend
- you can easily synchronize web browser actions and back-end operations from your unit tests

If you use a client in another language, you will have to find solutions to implement these interactions. Using Parasol, you can use what you had already set up to implement your application anyway.
These are the reasons we implemented and use Parasol, and why just using a binding implemented in another language is hardly an option.

cheers
Johan

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside