| || |
I recently read an article by Borland on how to convert to Agile development and they mentioned something about FitNesse. Do you guys know what is it? I went to their web site and saw that you can create some sort of test tables where you would specify your input parameters and expected values and then hit some sort of 'run' button and you get your results.
Do you know how exactly it works? More importantly, how does it work with SilkTest.
Thanks for your help.
Have you been to Starwest conference? Where did you get the article about this? I dont know the contents of it, but I am sharing what was in my mind when you speak of Fitnesse.
Fitnesse is all about putting test instructions in a Table form (Table Driven Automation Framework). I have used a automation framework written in dotnet whose test cases have
instructions written in tables (e.g. excel sheet)
Window : Control : Action : Input or Output
Literally following this way, a manual tester can write automation test cases, without knowing inner structure of its implementation. When you say run, silk test (if engine implemented in 4test) parses through each row and converts them to suitable instructions and then executes them on the AUT. My guess is Silk test is made to use Fitnesse libraries for creating actions on AUT and might have explained in the document which you are mentioning.
If you take selenium, it is also a "table-driven automation framework", you can very well observe that in the Selenium IDE with a table of instructions with two columns.
Action : Parameters
I found this guy's blog is good for Selenium and Fitnesse.
go through this site and if interested catch hold of his book on TestDriven .Net Development with Fitnesse
Thank you very much for you reply on this. I really appreciate it.
The article that I'm talking about is a public whitepaper (or something like this) on Borland's web site. Here's the link: http://www.borland.com/us/rc/lifecyc...esting-ng.html
They say nothing on how to use it, they just say that they can use FitNesse with Java and SilkTest. Honestly, I didn't get much from it.
So, another question. You mentioned that a table row gets translated into a command which then gets executed. That way people with no programming background could potentially write test cases.
How is that different form creating a data driven case? Or by using a data source (such as database or an Excel sheet). In other words, why would I consider using FitNesse over an Excel spreadsheet?
Thanks again for your help.
Wow, I actually get to answer one of YOUR questions instead of the other way around!
My company uses a framework exactly like the one you are talking about. Our Excel spreadsheets contain all of the navigation steps as well as the form data and verification data.
The main difference between using Excel spreadsheets and FitNesse is that FitNesse is a web server and a Wiki. All of the data is fed into and extracted from the Wiki.
I have been looking into FitNesse as well. We had a consultant give us a Silk Central class when we installed it recently and he mentioned FitNesse specifically. It was also mentioned in an agile testing webex given by Borland a few days ago.
The FitNesse website is www.fitnesse.org. It has some pretty good explanations and examples.
Hope this helps.
Thanks for the answer!
Well, that's why we all come here: to learn new things and help each other out! That's what makes this site great [img]/images/graemlins/wink.gif[/img]
In regards to FitNesse, I'm still kinda confused about this whole framework (I haven't spent much time looking at examples checking it out in detail). I guess, I'm still not sure how data is fed from the Wiki into the testcase.
I will do some more research as soon as I will get a few moments from my other projects and then I might ask a few more questions about it [img]/images/graemlins/smile.gif[/img]
Thanks again for your help Trip and nareshkanduru
Data driven automation can be useful for automating applications say insurance policies. here basing on the data selected the course of flow changes and you will write test case to handle situations when different data comes in.
Table driven automation framework, is something like you define keywords and make use of that (by business users or manual testers) and each keyword will define the action it has to perform. You might heard of Quality Centers BPT model is something similar to this. (Personally I dont like it)
To get more idea, take a look at this link
and check section 1.3 keyword driven automation framework model.
Oh ok so FitNesse=BPT I am glad I found this I was looking for that, I have personally used BPT and found it helpful, I will try with FitNesse
I heard Silk4j in Silk Test 2008 R2 is having support for writing test cases in Java and using eclipse as an editor. However i dont have any materials or help, how to do it.
Judging from this post I'm not convinced Fitnesse is actually any use to us.
[ QUOTE ]
FitNesse is not a general purpose test automation tool. It is not designed to be a test automation tool, it is designed to work with acceptance tests or executable specifications that are worked out together by the business, testers and developers. Such acceptance tests can and should be used for regression testing later, but FitNesse is not a general-purpose test tool. There are much better tools for that, and if you need UI automation testing, use one of such tools.
[/ QUOTE ]
That's kinda let the cat out of the bag...
Based on my very little experience of working with FitNesse, I don't see how it is different from unit testing. Developers will have to write something in order to allow fitnesse access certain points of application, so, why would they write FitNesse classes instead of NUnit/JUnit?
Yes, the beauty of FitNesse is that someone with no experience could go to a wiki page and input a few more values that we would like to test... So, unit test can do the same thing and run with a nightly builds automatically...
I don't know... In my opinion it is not worth it, but I could be wrong. If you guys feel otherwise, I wouldn't mind hearing your thoughts on the topic.