Hello, all. I’m wondering if anyone has experience with documentation and knowledge transferring, namely from developers to QA.
One thing that slows down my QA team is when we don’t know the coded logic behind something. Sure, we may have a test case that says to make sure some amount gets populated, but we may not know what the calculation is that results in that amount. A script may reference an auto-populated date, but how that date is determined?..beats us! Going forward we include calculations and logic like that in the test cases, or somewhere where it is visible to us. However, we have years’ worth of code and logic that have never been documented.
It would help us test better if we knew what the logic in the code is, but we don’t have access to the developer’s .NET code (separation of duties). Some of us don’t even have Visual Studio. QA would need to reach out to a developer and have them show and explain the code to us, which we don’t always have time for.
Does anyone have any tips, tools or process recommendations that makes this type of knowledge transfer easier? I’m afraid this will ultimately be a painfully manual process, to build up this type of documentation, but any suggestions would be super appreciated!