Yeah, that looks amazing!
1 Like
Also within the realm of practical is to require passing recoder test (on vanilla edu instance) be submitted with every pull request to kinetic repos going forward.
These tests could then be published to a library by patch version and partners/customers run them on our pilot during the test window.
As it is we donât even know what new features to test exactly.
2 Likes
Last time I looked at this the project had some dependancy issues, I reached to the email address in the documetation and they sort of got things working for me, however. I found that just sticking the project into vs code and fire up agent mode to fix the project up and I had recorder working with the examples in very short time. Which I am currenly short of now and shouldnât really be posting but it caught my eye. Really need to get a library of scripts setup with data in it
2 Likes
I would be surprised if this isnât already happening. The challenge here is handling the various module combinations, CSFs, verticalizations, single company, single plant, etc. In other words, what makes an instance âvanillaâ?
If we were to create a community test suite as a starter project, we would have to come up with a testing order to do authentication first, then some basic UI API testing, then screen interaction, etc.
Can you elaborate? Issues in the script code? Order of testing?
1 Like
This was as few months ago when I dug into it further. At the time (and it might have changed) They gave you a sample project that you put into VS code and spun upâŚSorry canât remember the full details. You needed to run npm install against the sample project they provided. Thatâs when I got errors. The WDIO component was out of date and there were a lot of warnings re deprecated dependencies etc. Thatâs when I took to copilot to just get me past it, once that was done. it worked for me.
2 Likes
Right. They may have a dozen or more major implementation types to test against for whatever level of QA they want to guarantee.
Then another preemptive group of CR candidates running tests on pilot data finds outliers.
So vanilla is whatever base/edu they choose to maintain and guarantee for CR
Then refine and publish vanilla tests for all.
Test run timing is important, yes. And even within UI thereâs 4x tests for CRUD. And within Update there a distinction between updating test created records vs preexisting records. For example, their tests may pass for crudding new supplier but they didnât test updating and existing in this case: PSA! Supplier Entry Broken - USA! PSA! USA! - #27 by timshuwy
Itâs a deep matrix but weâre moving in the right direction.
2 Likes
Looks like 4.0.0 is now on EpicWeb.
4 Likes
This looks very different than version 3. Not sure how to register or get started. Anything I tried for org id doesnât work
2 Likes
Same.
Itâs reaching out to an AWS site (3.234.81.250) on port 443. 
Itâs an Electron app and sure calls DataDog a lot!
1 Like