Replies: 7 comments 9 replies
-
@jakobrosenberg ,
|
Beta Was this translation helpful? Give feedback.
-
This is great!! I'll fix the Node 16 issue. |
Beta Was this translation helpful? Give feedback.
-
Do you know if it's possible to connect a self hosted runner to Github? If so we could replicate your setup and have full integration tests for PRs. |
Beta Was this translation helpful? Give feedback.
-
I have solved the Node 16 issues locally. You can try the branch here https://github.com/pycom/pymakr-vsc/tree/node-16 If it works for you, I'll merge it into the next-staging branch. |
Beta Was this translation helpful? Give feedback.
-
So close now. Any idea what could be the cause of this? What happens if you |
Beta Was this translation helpful? Give feedback.
-
a quick update: Unit TestsThe Unit tests were very simple to update to run under Jest, with the follow pro's ::
Integration tests But there are a few templates in typescript that implement this, that need to be reworked into .js test explorerreports in Github Actionsthis simplifies spotting failing tests
|
Beta Was this translation helpful? Give feedback.
-
I came across this too. It complicated detection of whether a device is running since the chunks can range from single characters, single lines and multiple lines. I think the affected test has been updated, so it might not affect you any more. If it does let me know and I'll have a look. As for Jest, I started migrating my projects away from Jest last year because of scalability, performance and ESM issues. It's actually why I have started the probs project. Except for code coverage, probs has the same pros, though some are still in development. The lack of exitcode=1 was accidentally removed, but has been readded. I'll try get a release out asap. Apologies for the lack of documentation. This is on my todo list. Enabling watch mode ( |
Beta Was this translation helpful? Give feedback.
-
to improve quality ive started to set-up a simple hardware CI test
Initial results:
Similar could be run on linux x64 , windows , and mac
additional work is needed to log the test results in a standard format (JUnitXML seems the common supported format) so that other GHA tools can work with it to provide better feedback and to join additional platforms.
Also currently the action-runner is only installed for my fork of the repo, but it can also be installed for an organization (PyCom)
Beta Was this translation helpful? Give feedback.
All reactions