Page MenuHomePhabricator

Audit usages of integration tests
Closed, DeclinedPublic

Description

https://gerrit.wikimedia.org/r/#/c/372383/ demonstrates that a single change to Parsoid's output HTML can break dozens of tests in MCS. This feels like it can be avoided.

While an integration test is useful for catching these changes, only one test should have failed in this situation and should have specifically been testing against the HTML output.

I suggest we simplify these tests either by converting them to unit tests or using smaller articles.

We should discard any tests that are not adding any additional value.

Event Timeline

It's not really dozens of tests. It affected two tests of the same page (one for mobile-sections, another for the formatted endpoint), but they have multiple HTML files associated with them. So, to me the question is: should we keep the HTML files?

What purpose do the HTML files serve?

I use them for debugging. I don't need them very often, though. So, if we want to get rid of them that wouldn't be a problem for me.

Sounds like we should get rid of them? I'm not clear how to use them to debug... not sure if that says something! :)

I don't mind removing the HTML files from the repo. I would probably put the writing of the HTML files behind a flag, so it can be used when needed.

This isn't really a duplicate; an audit would be useful in its own right to determine the scope of work needed to eliminate these.

LGoto closed this task as Declined.Oct 9 2020, 4:50 PM