Property tests

[lastmjs]

Property tests are one of the final remaining hurdles to 1.0 for Azle. These tests will thoroughly test most/all aspects of Azle.

Please create a comment in this issue with a "fixed" checkbox at the top of the comment for every Azle bug found during the property tests.

Essentially we will create one property test, similar to the example tests, per major concept in Azle. The main task of each property test is to create the arbitraries required for that test. At the highest level each test will have a canister arbitrary. The canister arbitrary will be composed of arbitraries for other aspects of the test, imagine query method arbitraries, update method arbitraries, etc.

• Should we add TypeScript type checking tests to each prop test? I think that might be good, just fail on a tsc check
• Think about testing the negative/error cases
• Make sure to test Result
• Abstract out the actor require with the caching
• get rid of module commonjs
• What about creating these types as global variables?
• Deeply understand float32/float64 differences
• We need to make sure that function names cannot be JS or Rust keywords

Property Tests

• Property Tests: Candid types #1390
• Property Tests: Canister methods #1391
• Property Tests: Call APIs #1392
• Property Tests: Canister APIs #1393
• Property Tests: Management Canister #1394
• Property Tests: Stable Memory #1395
• Property Tests: StableBTreeMap #1396
• Property Tests: Timers #1397
• Property Tests: Plugins #1398