Rhum v2.0 (Release Date: TBD)

[crookse]

Tasks

• [x] CLI options (#74)
• [x] Script to generate test file (#44)
• [x] Mock not taking arguments (#28)
• [x] Ability to assert what arguments a method was called with (#21)
• [x] Skip functionality (#16)
• [x] real-time results (#78)
• [x] make subcommand (#44)
• [x] ~Ability to test non-public members (#19)~ (Won't do. Users should use the Reflect API.)
• [x] ~--ignore option (#82)~ (Logic is no longer needed. run command checks files for Rhum namespace now.)
• [x] ~Rhum lifecycle diagram (#81)~
• [ ] Documentation (https://github.com/drashland/website/issues/227)
  • [x] Add v2.0 docs
  • [x] Add migration guide
  • [ ] Archive v1.0 docs, but let it be accessible through an Archive section

[ebebbington]

Maybe https://drash.land/rhum/v1, drash.land/rhum/v2 ?

[crookse]

@ebebbington, yea that will work. in the sidebar, we'll have an Archive section and a v1.0 link. That link will point to drash.land/rhum/v1.

drash.land/rhum will be updated to have v2 documentation. the good thing about our documentation setup is that we can build separate vue applications for both v1 and v2 documentation.

[ebebbington]

Oh wait, can we reuse the v1 docs? I’m thinking we may as well do this for each module (fml) but v2 docs would still have stuff from v1

[crookse]

Yea, so what we'll do is build the v1 docs and put the build in a /v1 directory. That covers archiving the v1 docs. Then we can iterate over our vue app to make it v2. i do think we should make a branch for v1 though and just keep it alive in case we need to update v1 docs and rebuild the vue app.

[ebebbington]

nice one on the description!

[crookse]

Changing release date to TBD. Reason being that we realized Rhum v2.0.0 is dependent on the CLI service; and the CLI service needs more planning.

[crookse]

Pushing back release date. No time to work on this. Will aim for July 1, 2021

[crookse]

Setting release date TBD... waiting for deno std to be stable. :/

[crookse]

new requirement: need to write up new article on why use Rhum v2

[crookse]

based on internal discussions, rhum v2 will most likely be a test double module. deno has moved towards test case nesting which is what rhum introduced in the early stages of deno, but it seems to be unnecessary now. rhum v2 (as of currrent discussions) will only support mocks, fakes, dummies, spies, and stubs. more to follow towards the planned release of v2

[crookse]

closing this v2 plan. no longer needed since we're moving towards being a test double module