On 24.05.2018 21:24, Daniel Hilst Selli wrote: > Hi everybody. > > I have been playing with cockpit for some time. Now I have a little library > that > create processes in the backend, which keep running until I stop then, so I > start wondering about how to do integration testing with cockpit, ... > > In cockpit I have these constraints: > > - cockpit.js is served by cockpit-ws, > - A pam session is created when user login on web interface, > > At the most what I have is some function calls that have side effects on > backend. My testing would be checking for these side effects on the backend, > like checking if some process started, or finished, or if some file was > created, > or if a database table was populated.. Usually we would execute tests over > nodejs but I don't now how to deal with pam session ...
The Cockpit starter-kit has lots of work in it for doing CI with Cockpit plugins and code. Does it help: https://github.com/cockpit-project/starter-kit See the documentation: https://cockpit-project.org/blog/cockpit-starter-kit.html https://cockpit-project.org/blog/cockpit-custom-test-framework.html Cheers, Stef
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cockpit-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]/message/NF4YBB2KFOTWGZXCARD73O4EMFQWMG36/
