Display results as :

Rechercher Advanced Search

Latest topics
» Run automated selenium test scripts from JIRA ondemand
Fri Dec 08, 2017 12:40 pm by azharuddin

» New! Appium Desktop
Sat Nov 25, 2017 3:51 pm by azharuddin

» Selenium WebDriver Integration
Tue Nov 21, 2017 1:06 pm by azharuddin

» how to connect DB in selenium webriver
Fri Oct 06, 2017 4:09 pm by anbarasi

» How find any text in browser screen and click on it?
Thu Oct 05, 2017 2:02 pm by sandeepkommineni

» Selenium Webdriver
Tue Oct 03, 2017 1:35 pm by PiyushBiswas

» GRID setup tutorial.
Wed Sep 27, 2017 4:29 pm by johnyapp

» Drag & Drop Between Windows Using Selenium Driver
Wed Sep 27, 2017 2:10 pm by 26rondel

» Check if window is closed / verify input
Sat Sep 23, 2017 10:21 pm by brainstir


Selenium with JUnit

View previous topic View next topic Go down

Selenium with JUnit

Post by nnk.mca on Tue Dec 22, 2009 3:40 pm


I am using selenium RC with JUnit Framework. So i want to know the advantages of using the JUnit with selenium RC?

Thanks in advance..


Posts : 3
Join date : 2009-09-08

Back to top Go down

Re: Selenium with JUnit

Post by Adviser on Tue Dec 22, 2009 6:29 pm


Junit is basically use for white box testing. But if you are using selenium rc with Junit, you are able to get feature of junit to test your application functionally. your code with be robust and specific to scenarios rather than full application.


* You don't need to implement inner classes which are very awful
and bloat your test codes. Instead you can use closures. Using closures
for writing your mock objects can make your test codes smaller and more

* File operations are very easy to implement thanks to
AntBuilder. How many times do you need to make some file operations
(delete, mkdir, ...) within your test codes? Doing this with is
not fun at all. Using AntBuilder for this purpose is a good thing,
since Ant is predestinated to do this job.

* If you are using SpringFramework you can easily create the
config files (application context) by using BeanBuilder. By using this
concept you don't need to put separate XML files in your test project.
Everything is integrated and centralized in your test class!


* No source code formatter for Groovy: This is a real disadvantage
for Groovy at the moment. If you are working in a team this could be a
nightmare: reading the code with different formatting, CVS compare is
difficult, ... are some examples to mention...

* The Groovy plug-ins (code completion, syntax coloring, ...) - at least for Eclipse - is still very buggy.

* You need to learn some new concepts like: closures - which is
also an advantage after you understand them! Without closures you
cannot implement inner classes in Groovy, which are mostly a must in
writing unit tests.

Hope this will help you.


Posts : 379
Join date : 2009-07-30
Location : India

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum