Loading...
Guest user 

First recorded build

 
All history
 
#73811 »
Result: Build cashtab-tests failed with exit code 1 Agent: buildagent5  ( <Non existing pool> pool)
Time: 14 Mar 24 12:58 - 13:02 (3m:24s) Triggered by: Phabricator Staging on 14 Mar 24 12:53
Branch:

Code coverage

Methods: 50.6%50.6% Blocks: 60.7%60.7% Lines: 61%61%

Build problems: 2 (2 new)

Problem reported from build script (1)
Build cashtab-tests failed with exit code 1  
Build failure condition (1)
Process exited with code 1 (Step: Command Line)  
 Loading build log messages...

90 tests failed (90 new)

CashTab Unit Tests (83)
<Alias /> Registered and Pending Aliases are correctly rendered 
<Alias /> Registered and Pending Aliases are correctly rendered when pending list is empty 
<Alias /> Registered and Pending Aliases are correctly rendered when registered list is empty 
<Alias /> Registered and Pending lists do not render when aliasValidationError is false and aliasServerError is populated 
<Alias /> Registered and Pending lists still renders when aliasValidationError is populated and aliasServerError is false 
<App /> A user with all valid wallets in savedWallets does not have any savedWallets migrated 
<App /> A user with legacy blank contactList in localstorage is migrated on startup 
<App /> Adding a contact to an existing contactList by clicking on tx history adds it to localforage and wallet context 
<App /> Adding a contact to to a new contactList by clicking on tx history adds it to localforage and wallet context 
<App /> Clicking "reply" on a Cashtab Msg correctly populates the SendXec to address and amount fields 
<App /> If Cashtab starts up with some settings keys missing, the missing keys are migrated to default values 
<App /> If Cashtab starts with 1.5.* cashtabCache, it is wiped and migrated to 1.6.* cashtabCache 
<App /> Navigation menu routes to expected components 
<App /> Setting "ABSOLUTE MINIMUM fees" settings will reduce fees to absolute min 
<App /> Setting "Send Confirmations" settings will show send confirmations 
<App /> Wallet with easter egg token sees easter egg 
<App /> We do not see the camera auto-open setting in the config screen on a desktop device 
<App /> We do see the camera auto-open setting in the config screen on a mobile device 
<CashtabTestWrapper /> We can render other pages by passing the route 
<CashtabTestWrapper /> With default props, renders App component 
<Configure /> We can add, delete, rename, contacts from the Configure screen, and add a savedWallet as a contact 
<Configure /> We can rename the active wallet or a saved wallet, we can add a wallet, we can import a wallet, we can delete a wallet 
<CreateToken /> If wallet has insufficient XEC, renders component but does not render CreateTokenForm 
<CreateToken /> If wallet has sufficient XEC, renders CreateTokenForm 
<CreateTokenForm /> User can input valid token parameters, generate a token, and view a success notification 
<Home /> Renders backup warning and QR Code if user loads with a new wallet 
<Home /> Renders the Home screen with API error 
<Home /> Renders the loading component while loading, then the Home screen 
<Receive /> Renders as expected on desktop, including copy paste functionality of clicking on the QR code 
<Receive /> Renders the Receive screen with QR code of expected width for smallest supported mobile view 
<Receive /> Renders the Receive screen with QR code of size that is fully viewable in extension dimensions 
<SendToken /> Accepts a valid alias 
<SendToken /> Displays a validation error for an alias without .xec suffix 
<SendToken /> Displays a validation error for an invalid address 
<SendToken /> Displays a validation error for valid alias that has not yet been registered 
<SendToken /> Displays a validation error if the user includes any query string 
<SendToken /> Displays expected error if alias server gives a bad response 
<SendToken /> Renders the SendToken screen with send address input 
<SendToken /> Renders the burn token success notification upon successful burn tx broadcast 
<SendToken /> Renders the send token notification upon successful broadcast 
<SendXec /> Clicking "Send" will send a valid tx with op_return_raw after entry of a valid address and bip21 query string with valid amount and op_return_raw params to Send To field 
<SendXec /> Get expected error msg and send disabled if bad response from alias server 
<SendXec /> If the user has minFeeSends set to true but no longer has the right token amount, the feature is disabled 
<SendXec /> Pass a possibly valid alias without .xec suffix to Send To field and get expected error 
<SendXec /> Pass a valid address and an invalid bip21 query string 
<SendXec /> Pass a valid address and bip21 query string with invalid amount param (dust) to Send To field 
<SendXec /> Pass a valid address and bip21 query string with op_return_raw param to Send To field 
<SendXec /> Pass a valid address and bip21 query string with valid amount and invalid op_return_raw params to Send To field 
<SendXec /> Pass a valid address and bip21 query string with valid amount and op_return_raw params to Send To field 
<SendXec /> Pass a valid address and bip21 query string with valid amount param to Send To field 
<SendXec /> Pass a valid alias and bip21 query string with invalid amount param (too many decimals) to Send To field 
<SendXec /> Pass a valid alias and bip21 query string with valid amount param to Send To field 
<SendXec /> Pass a valid alias to Send To field that has not yet been registered and get expected error 
<SendXec /> Pass an invalid address to Send To field and get a validation error 
<SendXec /> Pass valid address to Send To field 
<SendXec /> Pass valid alias to Send To field 
<SendXec /> Renders the SendXec screen with send address input 
<SendXec /> Valid address with valid bip21 query string with valid amount param rejected if amount exceeds wallet balance 
<SendXec /> We can calculate max send amount with and without a cashtab msg, and send a max sat tx with a cashtab msg 
<SendXec /> We can send a tx with amount denominated in fiat currency 
<SendXec /> rendered with params in URL Legacy params are not parsed as bip21 even if the bip21 param appears in the string 
<SendXec /> rendered with params in URL Legacy params. Address and value keys are set and valid. 
<SendXec /> rendered with params in URL Legacy params. Address and value keys are set and valid. Invalid bip21 string is ignored. 
<SendXec /> rendered with params in URL Legacy params. Address field is populated + disabled while value field is empty + enabled if legacy url params have address defined and no value key present 
<SendXec /> rendered with params in URL Legacy params. Address field is populated + disabled while value field is empty + enabled if legacy url params have address defined and value present as undefined 
<SendXec /> rendered with params in URL Legacy params. Params are ignored if only value param is present 
<SendXec /> rendered with params in URL Legacy params. Params are ignored if param is duplicated 
<SendXec /> rendered with params in URL No params. Send screen loads normally with no rendered input. 
<SendXec /> rendered with params in URL bip21 param - an invalid bip21 param shows validation errors but cannot be changed 
<SendXec /> rendered with params in URL bip21 param - valid bip21 param with amount and op_return_raw is parsed as expected 
<SignVerifyMsg /> Notification is rendered upon signature verification error 
<SignVerifyMsg /> Notification is rendered upon successfully signing a message 
<SignVerifyMsg /> Notification is rendered upon successfully verifying a message 
useWallet hook rendering in different localforage states An incoming tx message from the websocket causes the wallet to update 
useWallet hook rendering in different localforage states Cashtab loads wallet, settings, cache, and contactlist from localforage to context if they are present 
useWallet hook rendering in different localforage states Verify a processChronikWsMsg() new block event updates the `aliasServerError` state var upon a /prices/ endpoint error 
useWallet hook rendering in different localforage states Verify refreshAliases() updates the `aliasServerError` state variable upon an /address/ endpoint error 
useWallet hook rendering in different localforage states Verify refreshAliases() updates the `aliases` state variable on a successful /address/ endpoint response 
useWallet hook rendering in different localforage states XEC price is set in state on successful API fetch 
useWallet hook rendering in different localforage states XEC price is set in state to fiat currency of user settings on successful API fetch 
useWallet hook rendering in different localforage states processChronikWsMsg() does not refresh alias prices when aliasPrices exists, server and cashtab array length do match 
useWallet hook rendering in different localforage states processChronikWsMsg() refreshes alias prices when aliasPrices exists, server and cashtab prices array length do not match 
useWallet hook rendering in different localforage states processChronikWsMsg() refreshes alias prices when aliasPrices is null 
CashTab Unit Tests: <App /> Cashtab version >= 1.6.0 and < 2.1.0 (1)
A user with an invalid Cashtab wallet as the active wallet is migrated on startup 
CashTab Unit Tests: <App /> Migrating (version >= 1.6.0 and < 2.1.0) (2)
A user with an invalid wallet stored at wallets key has that wallet migrated 
A user with multiple invalid wallets in savedWallets has them migrated 
CashTab Unit Tests: <App /> Migrating from wallet/savedWallet keys (version < 1.6.0) (2)
A user with an invalid Cashtab wallet as the active wallet is migrated on startup 
A user with pre-2.1.0 valid wallets in savedWallets has them all migrated to new storage keys and new shape 
CashTab Unit Tests: <SendToken /> Accepts a valid ecash (1)
prefixed address 
CashTab Unit Tests: <SendToken /> Accepts a valid etoken (1)
prefixed address 

486 tests passed (all tests)

×

×

Pin build

Cancel
×

Add build comment

Cancel
×

Promote Build

×

Add build comment

Cancel
×

Mute test

×

×

Server communication failure

Server is unavailable

Server stopped or communication with the server is not possible due to network failure.

Server shutdown started.

Please relogin to continue your work.

×

Run Custom Build

×

TODO

Loading related builds...
Cancel
×

Responsibility

×

Edit tags

Cancel
×

Loading...

×

Are you sure?

Cancel
×

Cancel