Change Details

A few of the upcoming changes to improve the re-use of references will be implemented in the VisualEditor ecosystem. While doing that we might want to refactor some of it's internals. To be sure that we do not break any use cases lets review and increase the test coverage in the related code bases. This is an umbrella ticket for that cause.

A few of the upcoming changes to improve the re-use of references will be implemented in the VisualEditor ecosystem. While doing that we might want to refactor some of it's internals. To be sure that we do not break any use cases lets review and increase the test coverage in the related code bases. [] Main use cases on how references are used and re-used in #visualeditor should be covered by end to end tests [] Main Citoid use cases on how references are used in #visualeditor should be covered by end to end tests [] Make sure that we have a good (e.g. QUnit) test coverage of the JS code in the #visualeditor #Cite code [] Review the test coverage of the #citoid integration into #visualeditor

A few of the upcoming changes to improve the re-use of references will be implemented in the VisualEditor ecosystem. While doing that we might want to refactor some of it's internals. To be sure that we do not break any use cases lets review and increase the test coverage in the related code bases. This is an umbrella ticket for that cause.[] Main use cases on how references are used and re-used in #visualeditor should be covered by end to end tests [] Main Citoid use cases on how references are used in #visualeditor should be covered by end to end tests [] Make sure that we have a good (e.g. QUnit) test coverage of the JS code in the #visualeditor #Cite code [] Review the test coverage of the #citoid integration into #visualeditor