File access are slow and the unit test suite seems to do a lot of them. It would be nice to track file being opened/written, identify the test causing the file operation and adapt the test to use a mock instead.
Version: 1.23.0
Severity: normal
File access are slow and the unit test suite seems to do a lot of them. It would be nice to track file being opened/written, identify the test causing the file operation and adapt the test to use a mock instead.
Version: 1.23.0
Severity: normal
In theory yes that is something we would need to do. But there is no formalized effort to speed up MediaWiki tests and I am definitely not going to work on it.
If there is interest, please fill a new task.