Asserts in the Chrome end-to-end suite the four items from #150 and #151 that #188 left uncovered. Closes #295.
Three new tests:
A token added on Add Token by its contract address shows as a row, with its symbol, in the address screen's balance list.
TransactionDetail opened from the token screen: the persisted navigation stack on arrival ends in address-token, which the address screen's entry cannot produce. After Back it is one entry shorter, checked before the screen.
The token contract row's link is read off the anchor and must be the explorer's /token/ page. Nothing is followed, so no network call.
Not visible in the diff:
The network stub now answers symbol() and name() for the stub token with what the explorer stub reports. Before, both decoded as empty strings.
The stub token stays tracked for the rest of the run; the second test reaches the token screen through the row the first adds.
Each check failed against its own deliberate break, one at a time, with every other test passing:
Add Token's confirm showing the address screen without re-rendering it: the balance-list check.
The token screen's transaction row going Back to the address screen before opening the transaction: the stack on arrival.
Back from TransactionDetail popping one entry too many: the stack after Back.
The contract row linking to /address/: the link check.
Judgement call: Back is asserted on the stack for the token-screen entry only; the address-screen entry's Back is driven by existing tests but not asserted.
Model: opus-5-5
Asserts in the Chrome end-to-end suite the four items from https://git.eeqj.de/sneak/AutistMask/issues/150 and https://git.eeqj.de/sneak/AutistMask/issues/151 that https://git.eeqj.de/sneak/AutistMask/issues/188 left uncovered. Closes https://git.eeqj.de/sneak/AutistMask/issues/295.
Three new tests:
- A token added on Add Token by its contract address shows as a row, with its symbol, in the address screen's balance list.
- TransactionDetail opened from the token screen: the persisted navigation stack on arrival ends in `address-token`, which the address screen's entry cannot produce. After Back it is one entry shorter, checked before the screen.
- The token contract row's link is read off the anchor and must be the explorer's `/token/` page. Nothing is followed, so no network call.
Not visible in the diff:
- The network stub now answers `symbol()` and `name()` for the stub token with what the explorer stub reports. Before, both decoded as empty strings.
- The stub token stays tracked for the rest of the run; the second test reaches the token screen through the row the first adds.
Each check failed against its own deliberate break, one at a time, with every other test passing:
- Add Token's confirm showing the address screen without re-rendering it: the balance-list check.
- The token screen's transaction row going Back to the address screen before opening the transaction: the stack on arrival.
- Back from TransactionDetail popping one entry too many: the stack after Back.
- The contract row linking to `/address/`: the link check.
Judgement call: Back is asserted on the stack for the token-screen entry only; the address-screen entry's Back is driven by existing tests but not asserted.
Model: opus-5-5
Adding a token by its contract address is checked against the address
screen's balance list. TransactionDetail opened from the token screen is
checked on the persisted navigation stack, on arrival and after Back,
which is what tells it apart from the address screen's entry point. The
token contract row's explorer link is read off the anchor, not followed,
so it needs no network fixture.
The network stub now answers symbol() and name() for the stub token,
which Add Token reads; before, both decoded as empty strings. The token
stays tracked for the rest of the run.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Asserts in the Chrome end-to-end suite the four items from #150 and #151 that #188 left uncovered. Closes #295.
Three new tests:
address-token, which the address screen's entry cannot produce. After Back it is one entry shorter, checked before the screen./token/page. Nothing is followed, so no network call.Not visible in the diff:
symbol()andname()for the stub token with what the explorer stub reports. Before, both decoded as empty strings.Each check failed against its own deliberate break, one at a time, with every other test passing:
/address/: the link check.Judgement call: Back is asserted on the stack for the token-screen entry only; the address-screen entry's Back is driven by existing tests but not asserted.
Model: opus-5-5
PASS
Model: opus-5-5