I'm in the process of re-vamping our testing process across our organization which includes how we Unit Test and Business Testing, I had a thought the other day and was wondering if anyone else has had experience with both the Development Team and BA's using TD for the Unit and Business Testing purposes? Anyone have any pros or cons to this concept? There's a cost to it in getting licenses for developers et al, but I want conformity and this might the way to go!
All replies are most welcome!
Thanks In Advance
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
TestDirector was created as a test management tool regardless of the testing cycle and can be easily customized or organized to meet your needs. The manual test runner is great for Business Testing (replacing the spreadsheets that most business areas use). Of course, I would strongly suggest presenting a demo of the tool to the BA's and Developers to see what they think of the tool. I'd be prepared to get the most resistance from the Developers. If everyone agrees, I don't see a reason why TestDirector wouldn't make a great test management tool for all your test phases. Best of luck!
There is a testing tool that comes with TD, called VAPI-XP. You do not need additional licenses to use this tool.
Using VAPI-XP your developers can write a "black-box" unit tests against COM/DCOM, Java, Web Services and Console Applications, using any supported scripting language.
VAPI-XP supports the following script languages: VBScript, JSCript, PerlScript and PythonScript.
Also it is fully integrated with TD and has a full access to current TD session though connected OTA (Open TestDirector Architecture)
Alexei, Will VAPI-XP be supported long term in TD? I was at the Users Conference and asked this question. I got some mixed results depending on who I asked. What I heard is that the VAPI-XP functionality came from R&D and was not developed through product design etc. I asked these questions since it appears there is very little documentation or discussions on the use of this functionality and I'm concerend about putting an eggs in this basket without knowing Mercury's intent. At the moment I see the risk that this is not a widely adopted function and could be removed from the tool or not supported as well as other functionality.