Change Details

Hopefully this test allows us to take early action for issues like T165115. Steps I followed to makes this test: - i requested mobileview output from beta cluster for a specific revision of an article on the beta cluster - i placed this json in a fixture file - wrote a test which makes the same request from beta cluster for the same revision - the test fails if the requested section html differs from the sections stored in the fixture json That way we'll get notified the same day anything lands in beta which changes mobileview section html. Because the test only compares section html and tests a specific revision of the file it is hoped it will only fail if beta mobileview changes something affecting section html.

Hopefully this test allows us to take early action for issues like T165115. I added a new test which... - requests mobileview output from beta cluster for a specific revision of an article on the beta cluster - ensures equal number of opening and closing divs. same for spans. That way we'll get notified the same day any unbalanced divs or spans land in beta mobileview section html.

Hopefully this test allows us to take early action for issues like T165115. Steps I followed to makes this test:I added a new test which... - i- requesteds mobileview output from beta cluster for a specific revision of an article on the beta cluster - i placed this json in a fixture file - wrote a test which makes the same request from beta cluster for the same revision - the test fails if the requested section html differs from the sections stored in the fixture jsonensures equal number of opening and closing divs. same for spans. That way we'll get notified the same day anything lands in beta which changesany unbalanced divs or spans land in beta mobileview section html. Because the test only compares section html and tests a specific revision of the file it is hoped it will only fail if beta mobileview changes something affecting section html.