Page MenuHomePhabricator

[GOAL]: Testing practices & expose test coverage
Closed, ResolvedPublic

Description

Subgoals

  • Expose test coverage metrics on documentation site.
  • Expose test coverage metrics on each submitted patch.

Developing a testing culture

Why

Test coverage indicates what percentage of our code is tested and helps improve
the confidence and reliability when making changes.

Current situation

There's no (or little) insight into code coverage by our tests on our
properties.

We are fairly lax on adding and merging code without the proper coverage.

Objectives
  • Document how and expose test coverage of our properties.
  • Run coverage reports by patch. Notify.
  • Educate the team on the validity of a patch without tests. Training sessions.
  • Improve test coverage of the worst offender artifacts.
  • Ongoing mentoring and conversations, offsites, training
Estimated work

1 sprint ~25%

Related Objects

StatusSubtypeAssignedTask
Resolved Jhernandez
OpenNone
ResolvedLegoktm
StalledNone
OpenNone
OpenNone
ResolvedJdlrobson
DuplicateNone
OpenNone
OpenNone
ResolvedLegoktm
DeclinedJdlrobson
DeclinedJdlrobson
DeclinedNone
ResolvedLegoktm
DeclinedNone
DeclinedNone
ResolvedSpikeovasileva
OpenNone
OpenNone
Openpwangai

Event Timeline

Jhernandez claimed this task.
Jhernandez raised the priority of this task from to Medium.
Jhernandez updated the task description. (Show Details)
Jhernandez subscribed.
Jhernandez renamed this task from Testing practices & expose test coverage to [GOAL]: Testing practices & expose test coverage.Jul 31 2015, 4:26 PM
Jhernandez set Security to None.
Jdlrobson subscribed.

Closing given that we have code coverage reports in MobileFrontend: https://doc.wikimedia.org/MobileFrontend/master/js/lcov-report/mobile.startup/Browser.js.html and we are achieving both of the goals