v0.8.4
host-api-test-sdk 0.8.4
Two fixes addressing developer-reported issues. Drop-in upgrade from 0.8.3.
Fixed
getIsAuthenticated()now reflects login state (#25). Previously the flag defaulted totrueon page load, sosetLoginBehavior('reject')was silently ignored — the host short-circuited login with'alreadyConnected'. Now it startsfalse, flipstrueon successful login (orsimulateReconnect()), and resets tofalseon a rejected login. If your tests want a session pre-authenticated (e.g. forgetUserId), callsimulateReconnect()afterloadHostAndProduct.
Documented
- What
permissionLogrecords (and what it doesn't) (#24). New README section makes the semantics explicit: signing isn't gated behind ChainSubmit at the test-sdk level (deliberate 0.7.1 design),permissionLogonly records explicithostApi.permission(...)calls, andtransaction_broadcastdenials happen insidehost-containerand aren't observable from the test-sdk today. If your assertion was "rejected permission prevented submission", the right oracle is the product's error UI, not the permission log.
What you need to do
- Upgrade to
0.8.4. - If any test relies on
getIsAuthenticated()returningtrueon a fresh page, addawait testHost.simulateReconnect()(or run a login) before the assertion.