feat(ut):configloader ut #661

[himku]

UT BBD.yaml

given:
  - name: "Config"                                  
    modules:
      - name: "LoadConfig"                    # 对于configloader.LoadConfig函数测试
        behavior:
          - when: "Yaml Parses Success"             
              - specify: "should state filed correctly"   # 是否应正确存档状态
               - should: "state.backend equal s3 or local"  # 应该是s3 or local
               - should: "state.options.statefile equal devstream.state"  # 应该是devstream.state

              - specify: "Tools Options cannot be empty"
               - should: "Array Tools not nil"
               - should: "Tools.Name not empty"
               - should: "Tools.InstanceID not empty"
               - should: "Tools.Options not empty"
               - should: "Tools.DependsOn not empty"
          - when: "Yaml Parses Fails"
             - specify: "Yaml parses fails"
               - should: "err not nil"

Description

Add configloader Loadconfig some ut test cases

Related Issues

🍀 Proposal: Add More ut to the configloader Package #661

New Behavior (screenshots if needed)

• Correct configuration screenshots

• Error configuration screenshots

[IronCore864]

@himku thanks for the contribution!

We will test your change locally and try to merge it as soon as possible.

Please join our Slack here. Feel free to reach out and request to join the contributor channel! We are also in CNCF now; please also consider joining this channel in CNCF Slack.

In the meantime, feel free to check out our new contributor guide. We have quite a few pieces of documentation explaining the basic concepts and how to work on DevStream. Read them in the "Developer Guide" section of the documentation.

If you are searching for something else to work on, please do check out the "find an issue" section. The "help wanted" label is an excellent place to continue. If you are not completely confident yet, maybe you can warm yourself up by solving another "good first issue".

Regarding commit messages, we try our best to follow the conventional commits specification so that it would give other people clear information. We've also got a "TL;DR" version in our documentation; feel free to have a quick glance. Please provide useful information in your commit message; and please do not use duplicated commit messages.

You do not need to update your commit messages for this PR. We will use squash merge and update the commit messages accordingly. Please try to follow the standard next time :)