[Mixed Reality Auth] Smoke tests failing
See original GitHub issueThe samples for each package is used in our smoke tests, and the one for the Mixed Reality Auth package has been failing since the start
SMOKE TEST FAILURES
Exception: Error: accountId with value "<account identifier>" must be of type string and a valid uuid.
##[error]Test Failed - Package: mixedreality-authentication - Sample File:getToken.js
{
sample: {
entrypoint: [AsyncFunction: main],
name: 'mixedreality-authentication',
sampleFile: 'getToken.js',
directory: '/home/vsts/work/1/s/sdk/mixedreality/mixedreality-authentication/dist-samples/javascript'
},
result: {
success: false,
exception: Error: accountId with value "<account identifier>" must be of type string and a valid uuid.
at serializeBasicTypes (***/@azure/mixedreality-authentication/node_modules/@azure/core-http/dist/index.js:789:23)
at Serializer.serialize (***/@azure/mixedreality-authentication/node_modules/@azure/core-http/dist/index.js:583:27)
at getOperationArgumentValueFromParameterPath (***/@azure/mixedreality-authentication/node_modules/@azure/core-http/dist/index.js:5014:24)
at getOperationArgumentValueFromParameter (***/@azure/mixedreality-authentication/node_modules/@azure/core-http/dist/index.js:4985:12)
at MixedRealityStsRestClient.<anonymous> (***/@azure/mixedreality-authentication/node_modules/@azure/core-http/dist/index.js:4668:53)
at step (***/@azure/mixedreality-authentication/node_modules/tslib/tslib.js:143:27)
at Object.next (***/@azure/mixedreality-authentication/node_modules/tslib/tslib.js:124:57)
at ***/@azure/mixedreality-authentication/node_modules/tslib/tslib.js:117:75
at new Promise (<anonymous>)
at Object.__awaiter (***/@azure/mixedreality-authentication/node_modules/tslib/tslib.js:113:16)
}
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Smoke test fails on 1 or more isolation segments after ...
Smoke test app route points to unexpected domain. In other words, the wrong domain is mapped to an isolation segment. You see the...
Read more >Testing Methodologies: From Requirements to Deployment
Smoke tests usually prove that at least one user can log on (which proves that authentication works), for example, and often check for ......
Read more >What is Continuous Testing | IBM
Smoke tests: These tests, which can be manual or automated, provide an initial cursory screening for conspicuous flaws in software. While smoke ...
Read more >Virtual reality cognitive intervention for heart failure - NCBI - NIH
The purpose of this study is to test the preliminary efficacy of this latest version of Nature‐VR on attention, HF self‐care, and HRQoL...
Read more >Smoke testing in CI/CD pipelines - CircleCI
Smoke tests are designed to reveal these types of failures early by ... source $BASH_ENV gcloud auth activate-service-account --key-file ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@willmtemple I think converging the smoke tests into the live tests yml configuration OR having the script respect region defaults in the
test-resources.json
file is probably the most flexible approach that we can use across languages here.@willmtemple Looks like this is the case of environment variable values not getting picked up right. Can you help Craig here?