E2E postman tests

[torbacz]

Description

• Implemented E2E tests for WebServer using postman collection

Motivation and Context

• A road to parameters in URL :)

How Has This Been Tested?

• ESP32 with latest firmware
• Postman tests

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

[torbacz]

There are 2 requests that I can't get working. They are marked as "[NotWorking]".

[Ellerbach]

The file must be created before reading. So you have first to call the API to create the file, then you can read it.
And for the basic auth, what's not working?

[Ellerbach]

I've been adjusting the tests and also fixed few things (PR to come):

And a new json file:

nanoFramework WebServer E2E Tests.postman_collection.json

[torbacz]

The file must be created before reading. So you have first to call the API to create the file, then you can read it. And for the basic auth, what's not working?

I think that second issue was providing "Authorization:Basic" without any credentials. And then server hangs. But we can skip it for now.

[torbacz]

Collection updated. I think we can merge it now and create more tests as required in future.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[Ellerbach]

Thanks for adding this, it will be handy to make sure the web server always works as expected when we have changes on it!