You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the unit tests to verify that I had my eBay developer account set up correctly, and I found several issues with the unit tests.
For the GetAccessToken_EndToEnd_Production and GetAccessToken_EndToEnd_Sandbox tests the sign in page no longer has element id's of userid and pass, instead they are numeric and change for each visit to the sign in form. I didn't look at changing the logic to find the correct fields, I debugged the test case and manually gave access.
At least for my eBay developer account the values in the scopes list were only valid for the sandbox so GetAccessToken_EndToEnd_Production would fail with an invalid scope error.
XUnit no longer writes to the console. Instead it takes a ITestOutputHelper as an argument to the test constructor and saves the references. Then it uses that reference to log. The log results are available in the Test Detail Summary for each test.
The text was updated successfully, but these errors were encountered:
I used the unit tests to verify that I had my eBay developer account set up correctly, and I found several issues with the unit tests.
For the GetAccessToken_EndToEnd_Production and GetAccessToken_EndToEnd_Sandbox tests the sign in page no longer has element id's of userid and pass, instead they are numeric and change for each visit to the sign in form. I didn't look at changing the logic to find the correct fields, I debugged the test case and manually gave access.
At least for my eBay developer account the values in the scopes list were only valid for the sandbox so GetAccessToken_EndToEnd_Production would fail with an invalid scope error.
XUnit no longer writes to the console. Instead it takes a ITestOutputHelper as an argument to the test constructor and saves the references. Then it uses that reference to log. The log results are available in the Test Detail Summary for each test.
The text was updated successfully, but these errors were encountered: