Literate programming shouldnt necessarily apply to application code for large systems but I almost always want more literate tests that clearly explain not just

Literate programming shouldnt necessarily apply to application code for large systems but I almost always want more literate tests that clearly explain not just what should happen under all kinds of scenarios but why it does that. Even better if I had hyperlinked explanations for domain specific terms. If I always had this I think I'd become fully productive on large systems 2x as quickly. I dont think this need be achieved by hiring a unicorn coder who is also a great writer but by making tests more accessible and editable by good technical writers so that both parties can collaborate around behavioral tests that double as documentation.