Releases: onflow/flow-js-testing
v0.6.0
Minor Changes
-
#237
eceb9d6
Thanks @jribbink! - Allow loading service key from environment variables and files.BREAKING CHANGES
getConfigValue
andset
have been removed as these were just a confusing abstraction above the@onflow/config
packages- They have been replaced by exporting they
config
instance directly from the package
Patch Changes
v0.6.0-stable-cadence.4
Minor Changes
-
#237
eceb9d6
Thanks @jribbink! - Allow loading service key from environment variables and files.BREAKING CHANGES
getConfigValue
andset
have been removed as these were just a confusing abstraction above the@onflow/config
packages- They have been replaced by exporting they
config
instance directly from the package
Patch Changes
v0.6.0-stable-cadence.3
v0.4.0
Minor Changes
-
#155
9dcab53
Thanks @jribbink! - Allow custom transaction signers to be provided as object withaddr
,privateKey
,keyId
,hashAlgorithm
,signatureAlgorithm
keys as an alternative to supplying merely the signer's account address and having Flow JS Testing determine the rest. This allows for more complex transaction authorizers. See documentation for examples. -
#158
57edf7d
Thanks @jribbink! - Flow JS Testing now exports multiple new API methods:pubFlowKey
- may be used to generate an RLP-encodedBuffer
representing a public key corresponding to a particular private key.createAccount
method which may be used to manually create an account with a given human-readable name & specified keys.
And exports the following two enums which may be used with
createAccount
andsendTransaction
: -
#126
3fc34f3
Thanks @refi93! - Add getTimeOffset/setTimeOffset utilities, allowing to advance the time while testing smart-contracts -
#170
da5e666
Thanks @jribbink! - Emulator logs are now captured when callingexecuteScript
,sendTransaction
,deployContract
, anddeployContractByName
. They part of the tuple returned by these functions (i.e.[result, error, logs]
) and are provided as an array of strings. -
#142
9aecfdd
Thanks @jribbink! - BREAKING Bumped @onflow/fcl to 1.1.1-alpha.1Developers should note that
[U]Int*
andWord*
types are now decoded into strings by @onflow/fcl and no longer implicitly decoded into numbers. This means that these types will need to be explicitly converted to JavaScript Number types if required.This potentially affects the return values or event data for the following flow-js-testing features.
sendTransaction
(any[U]Int*
andWord*
event data will be decoded into a string instead of number)executeScript
(any[U]Int*
andWord*
return values will be decoded into a string instead of number)deployContract
/deployContractByName
(any[U]Int*
andWord*
event data will be decoded into a string instead of number)updateContract
(any[U]Int*
andWord*
event data will be decoded into a string instead of number)getBlockOffset
(return value will be string instead of number, and must be explicitly converted if JavaScript Number is required)
-
#166
69b25e0
Thanks @jribbink! - AddsignUserMessage
utility to sign a message with an arbitrary signer andverifyUserMessage
to verify signatures. See more here -
#117
033562b
Thanks @jribbink! - Dynamically select ports for emulator instead of supplying admin port statically through emulator.start arguments, deprecate use of this argument -
#129
78944c1
Thanks @jribbink! - Add optional error message match to shallRevert Jest assertion
Patch Changes
-
#207
a65ff32
Thanks @MaxStalker! - - Tests updated and double-checked.- Fixed regexp for log extracting.
- Added ability to skip transaction signatures validation.
- Updated GitHub actions to show code coverage report
-
#177
8d75426
Thanks @adbario! - Fix the warning about deprecated default compute limit for transactions -
#190
1ce23f0
Thanks @adbario! - Add explicit scoping to arguments for scripts in nested await functions to hint microbunde into doing the right thing -
#164
962b535
Thanks @jribbink! - Bump @onflow/flow-cadut to 0.2.0-alpha.7 (fixes bug where optional array, dictionary, path arguments did not work) -
#138
e807e83
Thanks @jribbink! - Version bump @onflow/flow-cadut (fixes "transaction" keyword not allowed in templates & adds PublicPath/PrivatePath/StoragePath/CapabilityPath argument compatibility) -
#149
fcabb81
Thanks @jribbink! - Fix flow-cadut imports that prevented CLI from working -
#192
31c5da0
Thanks @justinbarry! - Fix imports for flow-cadut generator -
#186
de917f0
Thanks @justinbarry! - No longer compress the packaged version of the library -
#165
4ac3741
Thanks @jribbink! - Block & timestamp offsets (e.g.setBlockOffset
/setTimestampOffset
now work in contracts. As well,deployContract
&deployContractByName
have the option of accepting code transformers like scripts/transactions.Additionally, passing the
builtInMethods
code transformer is now deprecated for scripts & transactions which require usage of block/timestamp offsets as transformer is applied by default internally by Flow JS Testing. -
#186
ff208e2
Thanks @justinbarry! - Add explicit scoping to arguments in nested await functions to hint microbunde into doing the right thing -
#144
d1eb29b
Thanks @jribbink! - Convert examples to run in Jest environment instead of ESM loader -
#188
f905016
Thanks @adbario! - Fix numbers as values deprecation warnings for tests -
#156
2206eda
Thanks @jribbink! - Bumped @onflow/fcl to ^1.2.1-alpha.0
v0.3.0-alpha.17
Patch Changes
-
#177
8d75426
Thanks @adbario! - Fix the warning about deprecated default compute limit for transactions -
#190
1ce23f0
Thanks @adbario! - Add explicit scoping to arguments for scripts in nested await functions to hint microbunde into doing the right thing -
#192
31c5da0
Thanks @justinbarry! - Fix imports for flow-cadut generator -
#188
f905016
Thanks @adbario! - Fix numbers as values deprecation warnings for tests
v0.3.0-alpha.16
Patch Changes
-
#186
de917f0
Thanks @justinbarry! - No longer compress the packaged version of the library -
#186
ff208e2
Thanks @justinbarry! - Add explicit scoping to arguments in nested await functions to hint microbunde into doing the right thing
v0.3.0-alpha.15
Minor Changes
-
#170
da5e666
Thanks @jribbink! - Emulator logs are now captured when callingexecuteScript
,sendTransaction
,deployContract
, anddeployContractByName
. They part of the tuple returned by these functions (i.e.[result, error, logs]
) and are provided as an array of strings. -
#166
69b25e0
Thanks @jribbink! - AddsignUserMessage
utility to sign a message with an arbitrary signer andverifyUserMessage
to verify signatures. See more here
Patch Changes
-
#165
4ac3741
Thanks @jribbink! - Block & timestamp offsets (e.g.setBlockOffset
/setTimestampOffset
now work in contracts. As well,deployContract
&deployContractByName
have the option of accepting code transformers like scripts/transactions.Additionally, passing the
builtInMethods
code transformer is now deprecated for scripts & transactions which require usage of block/timestamp offsets as transformer is applied by default internally by Flow JS Testing.
v0.3.0-alpha.14
Minor Changes
-
#155
9dcab53
Thanks @jribbink! - Allow custom transaction signers to be provided as object withaddr
,privateKey
,keyId
,hashAlgorithm
,signatureAlgorithm
keys as an alternative to supplying merely the signer's account address and having Flow JS Testing determine the rest. This allows for more complex transaction authorizers. See documentation for examples. -
#158
57edf7d
Thanks @jribbink! - Flow JS Testing now exports multiple new API methods:pubFlowKey
- may be used to generate an RLP-encodedBuffer
representing a public key corresponding to a particular private key.createAccount
method which may be used to manually create an account with a given human-readable name & specified keys.
And exports the following two enums which may be used with
createAccount
andsendTransaction
:
Patch Changes
v0.3.0-alpha.12
v0.3.0-alpha.11
Minor Changes
-
#142
9aecfdd
Thanks @jribbink! - BREAKING Bumped @onflow/fcl to 1.1.1-alpha.1Developers should note that
[U]Int*
andWord*
types are now decoded into strings by @onflow/fcl and no longer implicitly decoded into numbers. This means that these types will need to be explicitly converted to JavaScript Number types if required.This potentially affects the return values or event data for the following flow-js-testing features.
sendTransaction
(any[U]Int*
andWord*
event data will be decoded into a string instead of number)executeScript
(any[U]Int*
andWord*
return values will be decoded into a string instead of number)deployContract
/deployContractByName
(any[U]Int*
andWord*
event data will be decoded into a string instead of number)updateContract
(any[U]Int*
andWord*
event data will be decoded into a string instead of number)getBlockOffset
(return value will be string instead of number, and must be explicitly converted if JavaScript Number is required)