Add test case for if.

[liangyuanpeng]

Releated https://github.com/kcl-lang/kcl/issues/1410 Add a new test case for if.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• [ ] N
• [ ] Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• [ ] Affects user behaviors
• [ ] Contains syntax changes
• [ ] Contains variable changes
• [ ] Contains experimental features
• [ ] Performance regression: Consumes more CPU
• [ ] Performance regression: Consumes more Memory
• [ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• [ ] N
• [ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• [ ] Unit test
• [ ] Integration test
• [ ] Benchmark (add benchmark stats below)
• [ ] Manual test (add detailed scripts or steps below)
• [x] Other

[liangyuanpeng]

It's not clear what the cause of this problem is, but I hope the tests will cover it. cc @He1pa @Peefy PTAL,Thanks.

[He1pa]

It's not clear what the cause of this problem is, but I hope the tests will cover it. cc @He1pa @Peefy PTAL,Thanks.

I have found the error. It should be that lazy eval repeatedly executes the if statement when calculating _nodes. Im trying to fix it.

[liangyuanpeng]

@He1pa I just noted that https://github.com/kcl-lang/kcl/pull/1418 is merged and then i rebase main here, seems like it's still failing.

Testing /home/runner/work/kcl/kcl/test/grammar/if/if_stmt/test_5
STDOUT:
Condition is true.
Condition is true.
nodes: []

STDERR:

[Peefy]

Hello @liangyuanpeng Fixed in #1418 and #1423.

You can rebase the main branch, and update the test case to

_nodes=[]

if True:
    print("Condition: True") # Use the right YAML form
elif False:
    _nodes+=[]

nodes=_nodes

[liangyuanpeng]

Hi @Peefy Thanks for your quickly reply and work for it!

rebased main.

I have not get that why it's need to use the yaml data, In the real world, this is how people actually use it. Is this due to test case limitations?

--    print("Condition is true.")
++    print("Condition: True") # Use the right YAML form

[Peefy]

Hello @liangyuanpeng

At present, KCL's e2e testing only recognizes legitimate YAML data, which is different from real-world cases.

[liangyuanpeng]

Thank you for your clarification, updated

[coveralls]

Pull Request Test Coverage Report for Build 9594724261

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 71.274%

---

Totals
Change from base Build 9594420056:	0.0%
Covered Lines:	55602
Relevant Lines:	78012

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 9594724261

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 71.274%

---

Totals
Change from base Build 9594420056:	0.0%
Covered Lines:	55602
Relevant Lines:	78012

---

💛 - Coveralls