Fix: Some file tests that should have failed always pass in Github repo.

[piux2]

Description

#440 1 of 3

The actual is the same as and wanted results in the test file. However, in the run time, when go.parser parses the wanted comment, it recognizes up to two lines of // style comments. parser.ParseComments() already returns two newline max. Since prinln(renderedContent) returns three new lines, it always fails. Therefore, we can not use println in the file test if the rendered content already has two new lines.

replacing println() with print() will fix it.

How has this been tested?

1. set syncWanted=false in tests/file.go
2. make gnodev
3. make test.examples

[piux2]

Description:

#440 2 of 3

All these tests failed because we restructured the example naming space, and the package path changed. As a result, the package address and realm object hashes changed. However, the package address in std7.gno and realm object hashes in zrealm_exmaple.gno, zrealm_test0.gno still have the value before the changes.

How has this been tested?

1. set syncWanted=false in tests/file.go
2. make gnodev
3. make test.files2

[moul]

Thank you @piux2,

We need to make sure that the CI is failing when it should.
Do you think some tests may still be ignored by the CI?

[piux2]

Thank you @piux2,

We need to make sure that the CI is failing when it should. Do you think some tests may still be ignored by the CI?

Before we fix the syncWanted in step 3 of 3, CI ignores all file tests that need to match the output and realm objects. However, If we turn it off now, CI will fail for the above testing cases because the testing case needs to be updated. So the sequence is essential.

1 of 3 and 2 of 3 are to fix the testing cases. After merging, we can do step 3 of 3; I will check in the code that sets syncWanted=false and add syncWanted as a flag in the gnodev for local testing. After that, CI will fail on future changes that break the tests as expected.

[moul]

Great.