Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making stubs great again #4

Open
fredbi opened this issue Feb 5, 2018 · 1 comment
Open

Making stubs great again #4

fredbi opened this issue Feb 5, 2018 · 1 comment

Comments

@fredbi
Copy link
Member

fredbi commented Feb 5, 2018

@casualjim

Please don't ditch this repo: it is awesome, albeit unfinished work.
I'll try to revive it. I managed to make it up and running and I am starting to figure out the many shortcomings. That's quite a heavy task.

Here is a todo that came up after a couple hours tinkering with the package.

What remains to be done. Feel free to comment.

  • workable faker for numbers and integers, according to format (format given as Arg to ValueGenerator)
  • faker for date, date-time and duration formats (duration is simple starting from a random int and using random alternate text marshaller,
    date is not so complex: take time.Now() and subtract a random number of days then marshal as text
  • relocate the reseed at top level (as top level option)
  • taking into account validations (planned dev, but no actual implementation)
  • abide by generation flags to control when generating a passing case and a non passing case (currently not implemented)
  • faker for slices (with option to produce a parsable string using CollectionFormat)
  • a testable fixture generator to instruct a test client (or a unit testing program)
  • a spec walker (may reuse the one under development with validate) to generate test cases for parameters, headers and responses
  • a test case orchestrator to plan for a full coverage of validation points
  • rule-based option detection for simple types: the idea is to find a smart way to select the ValueGenerator according to rules
    • simple types and formats should provide straightforward rules
  • a fuzzy-er based on title and description tags, along the lines of what meqqa suggests
  • the idea is to detect proper options according to hints in title/doc
  • investigate go native solution for NLP (meqqa use Python)
  • limit the use of x-datagen extension tag
  • generate combinatorial test suite with required / non required / allowsEmpty items
  • find a way to customize the faker dictionary
@shahzaibaziz
Copy link

@fredbi I am in for contribution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants