OK, when OpenTAP was released I was already familiar with the framework and test concept - thanks @jeff.dralla for thinking I was a competitor spy., which I took as a compliment btw.
IMO, once you’ve created something with OpenTAP there’s no going back. A colleague mentioned the other day how they can blah, blah, blah in 5 minutes without having to learn yet another test automation framework. I probably couldn’t convince them, and they called it a YATAF. Quickly switching into defence mode and getting the hump about the ‘yet another’ jibe about my new beloved best framework, my retort was OpenTAP is TOTAF - the only test automation framework. We were well into the acronym spouting, religious-like arguments engineers get to when ‘discussing’ stuff. So, I realised a better acronym is needed to describe what OpenTAP is to the non-believers. Suggestions welcome.
Dragging myself back on topic, once the development with OpenTAP starts to flow, it is suited to rapid development and large complex projects. My issue is that as a small developer with no formal computer science training I’ve never really collaborated with more than a couple of other developers, and we tended to keep things pretty simple. Now I like simple, but I think there is ‘simpler’ and best practices, and I think I’m missing something.
I’ve started to look at packaging and how to distribute the code within an enterprise, collaborate with others and automate some tasks using devOps.
At the moment:
- Multiple projects are under a single solution.
- All projects build to a single dev folder or release folder.
- A package is created from the release folder and distributed from a shared network drive.
That’s all good, but I know it can be better, even without implementing a CI/CD strategy.
So I was curious what other developers do?
- Do you build to a single folder or to each project bin folder. and why?
- How do you use packaging? Do you pick up the dll from the project’s bin/debug | bin/release folder?
- How to you you make your package available?
- Should the package.xml file be stored in the repo with the project/solution?
- It was very simple to create a bundle package using ./tap package create -v ‘.\Packages\SDK\Dev\release_package_config.xml’ , but how difficult and time-consuming is this for a multi-project solution?
- How to get VS to create the bundle package at the of the release build?
- Should I look at moving to GitLab. How do I convince management, and is there a cost?
Something to kick off a conversation that has often kept me awake at night, sad I know.
My solution explorer: