[Guiness] ddescribe supported

[vicb]

@vsavkin we used to be able to use ddescribe in place of describe it would have the same effect as iit on a group of test. It seems it doesn't work any more, could you take a look at this ?
(I haven't tried but I think xdescribe was supported before, is it still supported now ?)

Thanks

[vsavkin]

xdescribe, and xit should work.

ddescribe works the same way it works in Jasmine, which is different from how, for instance, solo_group works in unittest.

The way it works in Jasmine:

1. If there are no ddescribe or iit blocks, all the tests get run.
2. If there are ddescribe blocks, only these blocks get run.
3. If there are iit blocks, ddescribe blocks get ignored. So only the iit blocks get run.

For instance,

    ddescribe("A", () {
        it("test A1", () {});
        it("test A2", () {})
    });

    describe("B", () {
        iit("test B1", () {});
        it("test B2", () {})
    });

will run only test B1.

This is the way it is working right now in Guinness (to mimic Jasmine, and I also find this way better).

Does it work like this for you? If it does, is it a problem?

Thank you,
Victor

[vicb]

It think my uc is #2 but all the suite is executed instead of ddescribe tests only

(IIRC we have xit tests)

[vsavkin]

I tried a few specs, and ddescribe worked correctly. Can you send me the name of the file you are trying to run, so I can continue troubleshooting?

[vicb]

Must have been date-spec.dart. thanks for looking into this.

On May 11, 2014 1:09:30 AM CEST, Victor Savkin [email protected] wrote:

I tried a few specs, and ddescribe worked correctly. Can you send me
the name of the file you are trying to run, so I can continue
troubleshooting?

---

Reply to this email directly or view it on GitHub:
#1029 (comment)

[vsavkin]

I've pushed a version of guinness (v0.1.3) that fixes the issue.

To upgrade Guinness in the Angular project you will have to change pubspec.lock. If you want I can create a PR with the changes to the pubspec.lock file.

[vicb]

Thanks Victor. Yes please submit a PR that "closes" this issue.

[vsavkin]

@vicb Just submitted PR #1032.