* adds the concept of a "store" to the test-proxy. This means that the server itself will have some code around push and pull of assets
* adding API and CLI options to set a target "store"
* tests and other errata to do with the change
For the most part, this being present is not a big deal. When onboarding services though, ignoring spellcheck errors is usually pretty nice to begin with. It's only after getting all the other integration points figured out do we actually care about those errors.
* [feature] add result publish utils and cli
* add jest for test framework and db testcase
* add generateResult unit test case
* publish completed event will combine all tasks result
* separate upload artifact to azure pipeline artifact with create pr
Signed-off-by: zzvswxy <zhouzheng@microsoft.com>
Testing on whatif enabled:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1594264&view=logs&j=80f7b2d8-9c8c-53b8-36c5-63dcddd43cb4&t=fd53712b-8238-551a-0702-451e8924fb63
| Central PR | Sync PR status | Sync PR status after work | Branch | Test branch |
|------------|----------------|---------------------------|--------|------------------------------------------------------------|
| Not exist | Open | No change | Keep | sync-eng/common-branch_cleanups-13342 |
| Not exist | Otherwise | No change | keep | sync-eng/common-branch_clean-13343 |
| Open | Open | No change | Keep | sync-eng/common-branch_cleanup-3342 |
| Open | Otherwise | No change | Keep | sync-eng/common-add-lang-product-slug-3368 |
| Closed | Open | closed | delete | sync-eng/common-test_cleanup-3351 |
| Closed | Otherwise | No change | delete | sync-eng/common-branch_cleanup_test-3367 |
| Not configure | Open | No change | keep | daily/2022-05-02-ci-failed(js) |
| Not configure | Otherwise | No change | delete | daily/2022-05-02-ci-succeeded(js) |
_**Notes: `Otherwise` means PR not exist or closed.**_
* [Test-Proxy] updating readmes for basic usage (#3345)
* Update actions target to main repo/branch
Co-authored-by: Scott Beddall <45376673+scbedd@users.noreply.github.com>
* Move pylintrc into the apistub folder and include in the WHL.
* Fix pylintrc path.
* Include pylintrc in MANIFEST.in
* Reintroduce package_data in setup.py
* fix: infinite loop for pager operation without response check in scenario test
* fix: wrong path/head/query type parser
* feat: use example value instead of placeholder of string value
* feat: user testsuite to do the mock test
* fix: only set object with status when lro finished
* test: update test snapshot
* fix: lint problem
* Initial Assets-Sync Proposal Document.
* Prototype of Assets-Sync Script 'tools/asset-sync/assets.ps1` and accompanying Pester integration test suite. To properly enable integration testing in CI, additional effort is still required.
* Test Helper can create local language and assets repo scenarios. This means that we can fully integration test individual conflict scenarios as they are discovered by users.
* Powershell Test YML enabling CI checks for a powershell project. 'archetype-sdk-tool-pwsh'. This is usable outside of the this specific commit's new code.
Co-authored-by: James Suplizio <jasupliz@microsoft.com>
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
* misspelling correction
* reflecting the new checkers in README, and updated pylint version
* versioning in readme
* updating astroid version
* adding the new links too
* updating numbers of checkers
* allowing the test-proxy to update the directory from which recordings are retrieved without restarting the proxy
* updating an expected failed scenario to check for a cross-platform invalid path
Wei Dong
praveenkuttappan
Ben Broderick Phillips
Chidozie Ononiwu (His Righteousness)
Scott Beddall
MS ZhouZheng
Chenjie Shi
Sima Zhu
Deyaaeldeen Almahallawi
microsoft-github-policy-service[bot]
Travis Prescott
Christopher Scott
Libba Lawrence
chunyu3
Charles Lowell
Albert Cheng
Patrick Hallisey