You seem to be the most familiar with ReCoder/WebDriver here on the list. As @kian.bennett mentioned, the documentation refers to a Starter Kit. I think this download was available on the Wiki site at qalabs.epicor.com at some point which was used to download the extension locally to side-load. I suspect that once the extension was available from the Chrome/Edge Stores, there was no need to download anything and we also lost the access to the starter kit.
There is no mention of Test ReCoder on EpicWeb. There is one Test ReCoder issue on EpicCare, but no other mentions. Online help for 2025.2 has no mention of Test ReCoder either. The ELC does have a couple of sessions, but the one lesson points to the inaccessible wiki.qalabs.epicor.com site. I opened a case, but maybe @karihagedorn, @timshuwy, or @bconner can shine some light on the end-to-end testing tool.
Havn’t seen the Starter Kit download but the extension is still here:
and the doc says this:
If your application uses Kinetic 2024.1(UXP 11.x), this WDIO 8 starter project is
expected to work flawlessly.
l If your application uses a different version of Kinetic, some web elements might
not work if it has been changed as part of application UI. If you encounter this
issue, please reach out to us [DL-TestReCoderAdmin@epicor.com] and we’ll
provide the artifacts for your application version.
I’m working on a side-by-side of Webdriver.IO and Playwright.dev for our 2025.2 launch. I want to use these scripts for software validation as well as testing patches and upgrades in the future. Of course, this only runs tests in the browser and not classic. I’m ankle-deep into Playwright so far but couldn’t work on ReCoder until Ben pointed out this download. The video on EpicWeb is very helpful and similar to the presentation I saw at Insights 2025.
@Mark_Wonsil - it looks like you got the answers you were after which is great.
As for my more recent experiences, we haven’t had many for a while. We were investing fairly heavily into ReCoder/WebDriver IO test scripts back in 2024 and had a good period of success with them but have since paused our efforts due to inconsistencies and issues that we kept running into during early Kinetic 2025.1 testing.
That being said, though, our requirements are a bit different to what I expect most will be as we need to process many scripts/scenarios with hundreds of transactions primarily against pre-release and early versions of Kinetic with tight release/validation windows.
Overall, it’s a tool that I would really like us to get back using regularly and see broadly used by customers. @jbooker, would it be possible to get all the latest artifacts for each Kinetic version uploaded to EpicWeb to make it easier?
It would be great to hear how everyone who is trying, or using it, now gets on.
I mean ideally Epicor would work on it with us because like you said @Callum_Stott it is an incredible tool if it works and it would allow customers to quickly and accurately test which helps everyone keep up with the cadence of upgrades which ultimately helps Epicor keep up with cadences.
I’m in the camp that thinks that Epicor cannot possibly test every single feature in the software. There are just too many use cases.
Similar to what Callum is suggesting, it might be helpful if we had some kind of shared test bank that users, and even Epicor, could use to test patches.
Basically, what Utah just said, but I don’t think Epicor can do it for everyone’s business process.
But you bring upa good point about difficulties managing version specific tests. Hopefully whatever the compatability issues are will settle down in the future but in the meantime it could be messy.
Looks like the Starter does have swapable dependencies so those are probably the artifacts you need.
I wonder how epicor does this to test patches to previous versions.
Perhaps a monorepo and maintain a shared tests dir and have mutliple version dirs each with it’s own package.json(?)
My hope is to have tests for each customization we’ve implemented. We’re not even live yet and cannot imagine finding the time to test everything in Pilot twice a year. Especially where it seems the window gets compressed from a month to 2 weeks between Pilot & Live roll outs.
EDIT: Oh and likely some tests for important features we rely on which seem not widely used. We’ve experienced regressions in project billing for example that’s delayed our implementation twice. Wait for one feature and another one breaks. Basically testing epicor should be doing but they’re clearly not.
Yeah, I 100% agree. There are far too many variables for Epicor, or any company, to test everything at the scale of Kinetic ERP. Just the combination of activated modules can lead to a fair amount of variability across full end to end processes.
Therefore, within the realms of being practical, what I think would be amazing is if Epicor, and partners, adopted a standard approach where all training exercises, based around an unmodified copy of the EPIC06 education company, were scripted using ReCoder and made available with the training documentation with each new Kinetic version.
Enabling existing processes (training documentation) to be leveraged and a fairly good basic coverage that can easily distributed and re-used as starting points by all partners and customers that could potentially end up contributing to the library. It would still be a fair amount of effort and cost to get up and running but the ongoing benefits for all could be huge.
That’d probably be a good question for [