Announcing Drift: A Spec-Driven API Provider Drift Testing Tool
“Every change breaks someone’s workflow” (https://xkcd.com/1172/) This is true for APIs: schemas can be contracts - but usually they can’t, and alone they aren’t. Spec validation helps to ensure your API does what it says it does. Contract testing provides visibility into consumer behaviour. Together, they’re a powerful combination — and until now, you needed separate tools and workflows to get there. We are proud to announce the release of Drift 🚀 Drift is our answer to: “does my API actually match its spec?“: ✅ Spec-driven - OpenAPI is the source of truth 👩💻 CLI-first - Run in dev, automate in pipelines 📝 Declarative - Deterministic, versioned-controllable test suites ✏️ Scriptable - Lua engine for hooks, custom validation and advanced workflows 🔌 Extensible - Add new capabilities through the plugin architecture 🙆♂️ Flexible - Run standalone or embed into existing test frameworks ...and, of course, it’s fully integrated into PactFlow’s contract testing workflows to provide the API integrity checks needed in the age of AI, where APIs are created faster than ever and the cost of drift is higher than ever. Read more about why we built it and where we’re taking it 👉 https://pactflow.io/blog/schemas-can-be-contracts/
How to launch app, freshly-built by Team Build, for GUI testing?
Hi, I've searched the help and forums but haven't found the answer - I'm sure this must be a silly question: I'm trying to schedule GUI regression testing on our applications as part of our nightly automated build. Team Build gets our C++ code from TFS each night and compiles/builds our applications. We now have a test project with test items linked to a Test Complete .pjs file located underneath the Visual Studio test project, with everything checked-in to TFS. The build service is set to run interactively so it can test the GUI. I've added the pre-/post- build events to copy the TC folder to the target directory. Team Build builds the code on a build agent VM called \\dev-agent, and the code ends up at C:\Builds\11\TFSProject\MySolution\bin on that machine. The TC project folder is getting copied there successfully. We also have a build drop location set up on the test controller itself, and the build output all ends up in a folder such as \\TFScontroller\Built Code\MyBuild\MyBuild_20150313.16, and again the TC project folder is getting copied there successfully. My question is - what is the recommended way of launching the freshly-build application at the start of each test? The location of the application to run changes with every build on the build controller (drop location), and the location on the build agent (where I'm assuming the tests and TestComplete will run) is also specific to that build agent (number "11" in my case, at present), and will be different if this build and these tests are run on a different agent, and also differ hugely from where they will appear on a tester/developer machine. Once the app is launched, all the clicking, checkpoints, etc., should all work, but I'm not sure at the moment how to actually start the application in the first place, ready for testing. Sorry if this is a stupid question - any help greatly appreciated! Thanks, Richard
