Grants:IEG/Lua libs for behavior-driven development/Timeline
This project is funded by an Individual Engagement Grant
Timeline for Lua libs for behavior-driven development
[edit]Timeline | Date |
Baseline for the community portal is up and running | 1. June 2016 |
Week 26; done initial setup, working on page indicators | 3. jul 2016 |
Week 27; changed to strategy patterns, working on final report | 10. jul 2016 |
Week 28; done class final report, documentation | 17. jul 2016 |
Week 29; nothing to report | 24. jul 2016 |
Week 30; working on extract status and invoke subpage, started on a common monitor user | 31. jul 2016 |
Week 31; working on logging, tracking categories, and a lot of refactoring | 7. aug 2016 |
Week 32; done console interaction, started on expectations | 14. aug 2016 |
Week 33; working on expectations, doc on notifications | 21. aug 2016 |
Week 34; working on expectations, start working on renders | 28. aug 2016 |
Week 35; done renders for result, started on frame, started on extractors | 4. sept 2016 |
Week 36; done extractors, started on README (sdd) | 11. sept 2016 |
Week 37; done missing tests, done introduction to basic idea | 18. sept 2016 |
Week 38; notes and a few tests on an alternate coverage model | 25. sept 2016 |
Week 39; nothing to report | 2. oct 2016 |
Week 40; nothing to report | 9. oct 2016 |
Week 41; nothing to report | 16. oct 2016 |
Week 42; nothing to report | 23. oct 2016 |
Week 43; nothing to report | 30. oct 2016 |
Week 44; remove use of extension data, refactor | 6. nov 2016 |
Week 45; i18n, indications of bug in pageprops | 13. nov 2016 |
Week 46; nothing to report | 20. nov 2016 |
Week 47; design, icons, refactor indicators | 27. nov 2016 |
Week 48; refactor, PSR-logging, logging, tracking categories, bug in pageprops | 4. dec 2016 |
Monthly updates
[edit]Please prepare a brief project update each month, in a format of your choice, to share progress and learnings with the community along the way. Submit the link below as you complete each update.
June
[edit]A basic portal is up and running on Help:Spec.
This is before project start, aka month 0, but after a question from FDC on how to do community outreach. The portal is pretty sketchy so far.
July
[edit]Set up the test environment, and figuring out the overall organization. Testing some alternate solutions.
Methods for identifying the correct page for test module, and invoke the method to get the test report. Most of this code is pretty general, and it is possible to repurpose the code for other frameworks. That is it is agnostic to spec-style testing, it only assumes tap-formatted reports.
Some basic documentation.
August
[edit]Buttons for the test panel works, and calls the correct exported method. Reports will then be collected from the Scribunto debug facility. The reports are assumed to be TAP13, with additional data as comments.
Work is ongoing on the expectations, that is the expect
and subject
library functions. Rewrote several times, in the end it is somewhat similar to the proof of concept.
Started on reporting and realization of the reports, it seems like compact and full text report should be sufficient, and probably a vivid html report.
September
[edit]Low activity, mostly documentation and notes on alternate solutions.
Awaiting reply on midpoint report.
October
[edit]Is your final report due but you need more time?
Extension request
[edit]New end date
[edit]15. December 2016 (The new end date is not clear at all at this point.)
Rationale
[edit]Have not been able to work on this project lately.
Extension request
[edit]Noting that a more recent and complete extension request was posted on 3 January 2019 at Grants talk:IEG/Lua libs for behavior-driven development#Extension request, new completion date. Program officer reply and approval was also posted there on 4 January 2019.
Approved new end date
[edit]30 June 2019
- New final report due date is 30 July 2019. -- JTud (WMF), Grants Administrator (talk) 23:06, 4 January 2019 (UTC)