Closed Ryan-Sanger closed 3 years ago
The "errors" you show is not from the extension, and looks like telemetry calls failing , most likly handled and expected. If you can run an export and copy the entire output from the console tab and share with me (or extension-support@mskold.com) - I can take a look at it and see if we can identify the issue
Hi Mattias,
Please find attached console log error:
oteTab.html:1 Access to XMLHttpRequest at 'https://<..>. visualstudio.com/_apis/ClientTrace/Events' from origin ' https://ms-devlabs.gallerycdn.vsassets.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Content?bundle=vss-bundle-basejs-v9GpWWBnsWqhM23ijhK2HfAqLowTXGUqZLDRsBCZbkfY=:5
POST https://<..>.visualstudio.com/_apis/ClientTrace/Events net::ERR_FAILED send @ Content?bundle=vss-bundle-basejs-v9GpWWBnsWqhM23ijhK2HfAqLowTXGUqZLDRsBCZbkfY=:5 ajax @ Content?bundle=vss-bundle-basejs-v9GpWWBnsWqhM23ijhK2HfAqLowTXGUqZLDRsBCZbkfY=:5 (anonymous) @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:314 c @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 (anonymous) @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 u.promiseDispatch @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 (anonymous) @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 t @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282
On Thu, Apr 22, 2021 at 10:28 PM Mattias SKöld @.***> wrote:
The "errors" you show is not from the extension, and looks like telemetry calls failing , most likly handled and expected. If you can run an export and copy the entire output from the console tab and share with me (or @.***) - I can take a look at it and see if we can identify the issue
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825162832, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTKBBYDZUH2OK5CIAJLTKCBG5ANCNFSM43NEYQOQ .
Sorry, here's a better looking console error log: oteTab.html:1 Access to XMLHttpRequest at 'https://<..>. visualstudio.com/_apis/ClientTrace/Events' from origin ' https://ms-devlabs.gallerycdn.vsassets.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Content?bundle=vss-bundle-basejs-v9GpWWBnsWqhM23ijhK2HfAqLowTXGUqZLDRsBCZbkfY=:5
POST https://<..>.visualstudio.com/_apis/ClientTrace/Events net::ERR_FAILED send @ Content?bundle=vss-bundle-basejs-v9GpWWBnsWqhM23ijhK2HfAqLowTXGUqZLDRsBCZbkfY=:5 ajax @ Content?bundle=vss-bundle-basejs-v9GpWWBnsWqhM23ijhK2HfAqLowTXGUqZLDRsBCZbkfY=:5 (anonymous) @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:314 c @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 (anonymous) @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 u.promiseDispatch @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 (anonymous) @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282 t @ vss-bundle-ext-core-vVIe5jWvDMpSEY_pCPb4RxSQM9ZNdWEtAObg3ywD14bU=:282
Thanks, Ryan
On Thu, Apr 22, 2021 at 10:28 PM Mattias SKöld @.***> wrote:
The "errors" you show is not from the extension, and looks like telemetry calls failing , most likly handled and expected. If you can run an export and copy the entire output from the console tab and share with me (or @.***) - I can take a look at it and see if we can identify the issue
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825162832, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTKBBYDZUH2OK5CIAJLTKCBG5ANCNFSM43NEYQOQ .
Still the same - I need the full console output - including all Information and warnings entries
Morning Mattias,
Please find attachment of console log with all information and warning entries.
Thanks. Ryan
On Thu, Apr 22, 2021 at 10:50 PM Mattias SKöld @.***> wrote:
Still the same - I need the full console output - including all Information and warnings entries
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825176386, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTIZNOJ3Z3ZHKPNB3ELTKCDZZANCNFSM43NEYQOQ .
10[Violation] Added non-passive event listener to a scroll-blocking
Hi Mattias,
Received additional error messages when switching between Define tab and Offline test execution. See attached console log
[image: image.png]
On Fri, Apr 23, 2021 at 7:06 AM Ryan Sanger @.***> wrote:
Morning Mattias,
Please find attachment of console log with all information and warning entries.
Thanks. Ryan
On Thu, Apr 22, 2021 at 10:50 PM Mattias SKöld @.***> wrote:
Still the same - I need the full console output - including all Information and warnings entries
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825176386, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTIZNOJ3Z3ZHKPNB3ELTKCDZZANCNFSM43NEYQOQ .
10[Violation] Added non-passive event listener to a scroll-blocking
So now we found the error - not sure if thats the one you was thinking of ?
TypeError: Cannot read property 'querySelectorAll' of null
at TestHelper.js:47
at Array.forEach (
This indicates a bad test case (strange/unexpected format in the field Microsoft.VSTS.TCM.Steps)
I will look into making this "safer" so it doesnt crasch, but Im not sure then we can get a new version out to the marketplace. Short term solution would be to locate and fix the strange test case...
Is something to do with shareparameters?
If so, can we pinpoint which test case(s) is causing the problem?
On Fri, Apr 23, 2021 at 7:30 AM Mattias SKöld @.***> wrote:
So now we found the error - not sure if thats the one you was thinking of ? TypeError: Cannot read property 'querySelectorAll' of null at TestHelper.js:47 at Array.forEach () at Object.scanSharedStepsAndParameters (TestHelper.js:43)
This indicates a bad test case (strange/unexpected format in the field Microsoft.VSTS.TCM.Steps)
I will look into making this "safer" so it doesnt crasch, but Im not sure then we can get a new version out to the marketplace. Short term solution would be to locate and fix the strange test case...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825397294, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTMZXQMANQNVIRQYJTDTKEAWLANCNFSM43NEYQOQ .
A quick look said it was the test step field (Microsoft.VSTS.TCM.Steps) Making a work item query with test cases and including the test steps field would probably reveal the problem
found problem - there were missing steps in some of the test cases. strange it did not copy /export the test cases.
Can you possibly send me a query to export the test cases?
Thanks.
On Fri, Apr 23, 2021 at 8:21 AM Mattias SKöld @.***> wrote:
A quick look said it was the test step field (Microsoft.VSTS.TCM.Steps) Making a work item query with test cases and including the test steps field would probably reveal the problem
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825419040, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTJ5DYEGPOA5TSTBRGTTKEGVFANCNFSM43NEYQOQ .
There is no "query" to export test cases. If there where we wouldn't need to build an extension for it. (What I was saying is to find the failing test case having a work item Query showing the test step field for all test cases would show them quickly)
To completly render a single test case you need to evaluate the content of the test case, fetch other data , evaluate them and potential fetch other data in a recursive process.
Thanks Mattias for all your help and advice.
Really appreciate it.
Regards, Ryan
On Fri, Apr 23, 2021 at 9:20 AM Mattias SKöld @.***> wrote:
There is no "query" to export test cases. If there where we wouldn't need to build an extension for it. (What I was saying is to find the failing test case having a work item Query showing the test step field for all test cases would show them quickly)
To completly render a single test case you need to evaluate the content of the test case, fetch other data , evaluate them and potential fetch other data in a recursive process.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825449476, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTN7IR4K3COU3WJYCV3TKENSLANCNFSM43NEYQOQ .
Oh yes, wanted to know if the exported Offline-Test-Execution-Extension plugin can include the tags as well?
It would be great.
On Fri, Apr 23, 2021 at 9:53 AM Ryan Sanger @.***> wrote:
Thanks Mattias for all your help and advice.
Really appreciate it.
Regards, Ryan
On Fri, Apr 23, 2021 at 9:20 AM Mattias SKöld @.***> wrote:
There is no "query" to export test cases. If there where we wouldn't need to build an extension for it. (What I was saying is to find the failing test case having a work item Query showing the test step field for all test cases would show them quickly)
To completly render a single test case you need to evaluate the content of the test case, fetch other data , evaluate them and potential fetch other data in a recursive process.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALM-Rangers/Offline-Test-Execution-Extension/issues/48#issuecomment-825449476, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATZQKTN7IR4K3COU3WJYCV3TKENSLANCNFSM43NEYQOQ .
Currently not, and Im not sure what the use case for it would be.
To be clear - the intended use case is to be able to do test execution offline and get the results back to tfs/ado. Its not an export tool for test cases.
There are other tools both from Micrsoft and other vendors (I have the Enhanced Export PRO on the marketplace) to support exporting test case data.
Using Offline Test Execution Extension I'm unable to export 200 test cases The overlay or pop-up message box is displayed i.e. Fetching testpoints...[ESC to cancel]
Got following error on console:
Tried exporting 4 test cases and works fine.