You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
Don't print this unless you have to :)
>> >> To post to this group, send email to email@example.com.
>> >> To unsubscribe from this group, send email to
>> >> For more options, visit this group at
>> > --
>> > with regards
>> > RaghuNandan
>> > Do you know that it takes 10 litres of water to produce 1 sheet of A4 paper?
>> > Don't print this unless you have to :)
>> > --
>> > You received this message because you are subscribed to the Google Groups
>> > "Selenium Users" group.
>> > To post to this group, send email to firstname.lastname@example.org.
>> > To unsubscribe from this group, send email to
>> > For more options, visit this group at
>> Thomas Sundberg
>> M. Sc. in Computer Science
>> Mobile: +46 70 767 33 15
>> Twitter: @thomassundberg
>> Better software through faster feedback
> You received this message because you are subscribed to the Google Groups "Selenium Users" group.
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to firstname.lastname@example.org.
Easier to point you towards Liz Keogh here:
Now that you know that ATDD and BDD are the same thing, you need to stop worrying about using a “ATDD” or “BDD” tool. Tools can be used for many things, it all depends on how you use them. Selenium can be used as a ATDD/BDD tool if you want it to be, it’s all about how you decide to build your test framework for its use and how you lay out your tests. You don’t even need a separate Given, When, Then story file, you can do it all programmatically with something like http://code.google.com/p/yatspec/.
There is no one size fits all tool for everything; you will need to adapt the tools that you have to achieve what you want. So if there is no UI don’t use Selenium, use an appropriate tool for the job in hand.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/Eww81pTbUhwJ.
For more options, visit https://groups.google.com/groups/opt_out.
Where I am working right now we have weekly sprints and use Selenium to automate everything on the web page we are producing, we don’t use fitnesse, or cucumber or jbehave. So no it doesn’t mean you can’t use Selenium.
Automation is one of the best ways to make regression testing easy, there is nothing that says you can’t write your regression scripts as soon as you get the product in front of you. We don’t classify a story as done until exploratory testing has been completed and working automated scripts have been written. These scripts are then run every full build of the product (and all devs need to do a full build before checking code in). This means that anything that breaks the tests is picked up very quickly and we are almost always in a state where we can release a new version of the site after a new code check in.
There is no single defined way to work in an agile environment, what we are doing probably isn’t classed as BDD/ATDD because we are not always writing the automaton scripts before the code (It all depends upon time constraints, some are written in advance some are written as the code is completed). We do perform TDD though, none of the code is written before unit tests are produced. The whole point of agile is that you tweak it to work for you and your team, there is no defined right or wrong way, there is a series of principles and you can decide how to implement them to ensure that you have a happy and productive team.
In my mind the thing that will decide when you write you Selenium test will be your experience in writing automated test scripts and your familiarity with Selenium. The more experienced you are the more likely you will be able to write something useful in advance.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/LPUiDOL8l3sJ.
One possible option would be creating page objects.
You can then write your test using the page object and retrospectively add the @FindBy annotations to locate the WebElement’s that you are going to use when the code is available.
This of course assumes that you are going to know the basic structure of the page in advance and you will probably need to tweak them when the real code is available, but it can give you a basic structure to start from. In my mind BDD implies that you work very closely with the developers (that will most likely include pairing with them at some point), it’s very hard to try and write tests for fetures that are being developed if you are not part of the development process.
As David has said, it varies from team to team and depends on your interpretation of agile. One person’s BDD is another person’s WAgile…
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/qcAwQK8h_jEJ.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/3WmSLTKFK6wJ.