acceptance-testing

Ruby has this great abstraction layer on top of Selenium called Capybara, which you can use do functional/acceptance/integration testing. It also has another library called Cucumber which takes this a step further and lets you actually write tests in English. Both libraries are built on top of Selenium, and can be used to test against any major browser, but because of their abstraction layers it's super easy to write tests using them (well, as easy as functional testing gets at least). My question is: does Python have anything like that? I have found Pythonistas doing functional testing with

I'm a newbie try to test my Rails project using Capybara, but I'm confused with the meaning of page and page.body, when I try to detect some string from my div: (in :js=>true mode) <div>"some content"</div> Some of my test will pass with page.should have_content "some content" Some will pass with page.body.should have_content "some content" I try to puts the content but only "page.body" will give me some valuable information, the "page" itself will show me nothing, and I can't find any solid explanation about what page and page.body did. Can anyone help me? page is the current Capybara session

I'm attempting to set up SpecFlow for integration/acceptance testing. Our product has a backing database (not a huge one though) in Sqlite. This is actually proving to be a slightly sticky point though; how do I model the database for the tests? I would like to know what patterns others out there use for doing integration/acceptance testing with backing databases. I can think of the following approaches: Compile a database into the assembly with the tests, then shadow-copy it for each test. Seems slow though. I could create the database in memory and populate it with pre-determined data. I

Has anyone found a way to run Selenium RC / Selenium Grid tests, written in C# in parallel? I've currently got a sizable test suite written using Selenium RC's C# driver. Running the entire test suite takes a little over an hour to complete. I normally don't have to run the entire suite so it hasn't been a concern up to now, but it's something that I'd like to be able to do more regularly (ie, as part of an automated build) I've been spending some time recently poking around with the Selenium Grid project whose purpose essentially is to allow those tests to run in parallel. Unfortunately, it

What is the recommended practice? Should I add the my sub-folder under the fitnesse folder to version control? Context: working on a single developer rails pet project. I've my rails project under version-control (Subversion) however my fitnesse wiki pages lie under the fitnesse program folder. Fitnesse seems to have its own version-control... (I see numbered zips along with each of my wiki pages) Is it reliable? Where does it store the revisions? Use the -d switch ( which is surprisingly low profile on a google search ) Fitnesse20081201>run -p 8080 -d c:/projects/MyProjectNeedsAcceptanceTests

Do you need something like Fitnesse , if you have BDD tests? BDD "tests" exist at multiple different levels of granularity, all the way up to the initial project vision. Most people know about the scenarios. A few people remember that BDD started off with the word "should" as a replacement for JUnit's "test" - as a replacement for TDD. The reason I put "tests" in quotes is because BDD isn't really about testing; it's focused on finding the places where there's a lack or mismatch of understanding. Because of that focus, the conversations are much more important than the BDD tools. I'm going to