Closed ghost closed 8 years ago
I have heard of it, but haven't tried it yet. I will look into it for the next release.
Nice :smile:
Maybe I can help with the travis.ci custom test for this project. Overtime, I'll send a pull request to update the travis lint (if used) for this project.
Thanks.
If you want to help set up tests, I could add you as a contributor when I start work on a new version (which I'll do when I finish the docs).
I will not promise that I can really help, but I can try. Travis tools are somewhat fun to explore and useful to have.
Oh, I just realized there's another good alternative called CircleCI. I can debug the code through it on the fly, and running linux commands, while builds is automated. Since this PythonOS is GUI based, CircleCI might be better for this task, cause it will need user input(mouse events, clicks).
Oh I forgot. These integrated automated testing doesn't support GUI. So, it's pretty much useless for this project, unless you wanted to build non-gui codes like docker, java spring, rails and stuff.
That's alright. It may still be useful if I decide to make a backend of some sort (such as an app server or something).
Hey @furmada , did you ever tried travis.ci for automatic test for this repo? It seems gonna save a lot of time finding Python specific bugs with the testings. You also can customize the testing to suit this project, and maybe set a test rules for any other contributors in the future for this project.
Thanks.