-
Georges Racinet authored
This makes the `heptapod` fixture hold user password and private token information, something that we may want to revisit later, but that is simple enough for now. At instance creation, we generate a new private token for the root user, as it seems that the initially displayed value is not activated. Upon normal login, we retrieve the user private token, and store it in the `heptapod` fixture, along with its password. This should also enable us to stop hardcoding the root password and makes us close to be able to support tests running with regular users.
3074e12a0d71