mgivney / easyb

Automatically exported from code.google.com/p/easyb
0 stars 0 forks source link

Partially implemented tests should get the result "pending" #143

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
If I add functionality to my software which changes the implementation of
my existing tests, then I'd expect the test (which is then only half
implemented) to get the result pending. Instead the added line is ignored
and the result remains that it is run without failures.

Here's an example of what I mean:

scenario "deleting a user", {
    given "a user from a list of users", {
        user = userRetriever.getUser(ownerkey);
    } 
    when "an administrator deletes a user", {
        userSaver.deleteUser(user.getId());
    } 
    then "the user should be deleted from the list", {
        userRetriever.getUser(user.getId()).shouldBe null;
    }
    and "all his books should be deleted", {
        key = new SearchCriteria();
        key.setOwner(user.getId());
        books = bookRetriever.getAllBooks(key,qp);
        books.size().shouldBe 0;
    }
    and "the collections he owns (alone) should be deleted as well"
}

I want to add "collections" functionality to my library and still need to
implement this part of my test.

I'm using version 0.9 of the maven-easyb-plugin (on Windows).

Original issue reported on code.google.com by s...@sahisgreenhouse.nl on 23 Jul 2009 at 11:32

GoogleCodeExporter commented 9 years ago

Original comment by ajglo...@gmail.com on 8 Sep 2009 at 1:25

GoogleCodeExporter commented 9 years ago

Original comment by richard....@gmail.com on 19 Dec 2010 at 4:43

GoogleCodeExporter commented 9 years ago

Original comment by richard....@gmail.com on 19 Dec 2010 at 5:04

GoogleCodeExporter commented 9 years ago
Tested and confirmed working in test org.easyb.ConsoleCounterGetsItRight.story 
- easyb-core.

Original comment by richard....@gmail.com on 22 Dec 2010 at 4:16