Skip to content

issues Search Results · repo:pwyf/bdd-tester language:Python

Filter by

14 results
 (59 ms)

14 results

inpwyf/bdd-tester (press backspace or delete to remove)

Testing large files is like wading through treacle, and renders this unusable for our purposes. I tried swapping out behave for foxpath, and saw significant performance gains. Behave probably does a ...
  • andylolz
  • 1
  • Opened 
    on Dec 1, 2017
  • #17

I can’t tell what’s causing this at all, but I’m just going to: 1. Leave this issue as a placeholder 2. Go back to using DQLogFormatter (but I’ll leave DQJSONFormatter as default) @edugomez have you ...
  • andylolz
  • 1
  • Opened 
    on Nov 21, 2017
  • #16

@edugomez points out that this testing tool is sorely lacking some tests. Valid point! He also recommends using pytest.
  • andylolz
  • Opened 
    on Sep 19, 2017
  • #14

This split should affect only rules that are different between versions. Common rules across versions should be reused by all versions.
  • edugomez
  • 1
  • Opened 
    on Aug 17, 2017
  • #11

Options here. Pumpkin? Squash? Calabash? ~Zucchini?~ Naming things is hard.
  • andylolz
  • 3
  • Opened 
    on Aug 10, 2017
  • #10

It would be really handy if the folder structure of the features was somehow reflected in the output dict… E.g. dicts of dicts for nested folders, that sort of thing.
  • andylolz
  • Opened 
    on Jul 13, 2017
  • #9

It’s convenient to keep the features and steps in here, but it’s not necessary, and isn’t really correct. At some point, these should be moved each into their own repository.
  • andylolz
  • 1
  • Opened 
    on Jun 27, 2017
  • #8

We need a param to specify where the logging should go (e.g. a filename) and then environment.py should output it there. Refs #5.
  • andylolz
  • Opened 
    on Jun 27, 2017
  • #7

the API bit is very sparse at present.
  • andylolz
  • Opened 
    on Jun 27, 2017
  • #6

Okay so there are three different outputs: 1. Summary of results i.e. pass/fail/not relevant activity counts per scenario 2. Log of reasons for each activity failing each scenario 3. General informational ...
  • andylolz
  • 4
  • Opened 
    on Jun 13, 2017
  • #5
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub