sorry for the late reply!
Daniel Hilst Selli [2018-05-24 16:24 -0300]:I'm afraid I don't fully follow what you mean above. But if you just need to
> 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 ...
set up cockpit to avoid the login page and the PAM, you can configure ws to
use the "cockpit-stub" negotiation (i. e. none at all). E. g. welder-web does
that for its testing:
The main itch here that this is being shipped by the cockpit-kubernetes
package, so you need to install that (and its dependencies).
MartinList Archives: https://firstname.lastname@example.org/message/ELIHAUVUDLYSDL6AAKDCKPGR4VHZQXFL/
cockpit-devel mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines