Tag Info

Hot answers tagged

1

Testing at the API level is quite possible, and usually well worth the effort, especially when there are multiple consumers for that API, or if the API is available for public use. There is a related question/answer you might want to read through here: How do you test a backend API As far as tools for a REST web service, there are a number of options. You ...


1

Great idea a manual test runner and reporter for Cucumber. Seems someone has similar ideas and put it online: Cucumbumler, see https://github.com/TimWalker/cucumbumbler/wiki and http://technicaldebt.com/manual-cucumber-tests/ for a concept If this doesn't work out of the box, it should not be to hard to create something similar from scratch. You can ...


1

To be honest this sounds like the very issue that seems to have split the BDD tools. You either have tools that produce specifications during the test runs, ao that you know exactly what your system is capable of doing. Or you have tools that consume specifications so that you know how compliant your application is with the specifications. In the first case ...


1

This kind of depends on what the structure of your project actually is. So far your tests all seem concerned with the operation of the system as a whole, i.e. You appear to be doing only black box testing. If you want to test the units independently then you know need to open up the system and look inside it (white box testing). In this case you have ...


1

Specflow and Fitnesse approach the process of testing in two different ways. The process of passing inputs into your tests is very much a way of exploring the functionality of what the system can do. BDD however is all about defining scenarios that define exactly what the system should do. As a result, I would susggest the execution pattern for these ...



Only top voted, non community-wiki answers of a minimum length are eligible