When you are running msTest from the command line be sure you are correctly
referencing the unit test project.
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Erik Burggraaf
Sent: Tuesday, June 4, 2019 9:47 AM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: [URGENT] Unit Testing using Visual Studio
I was reluctant myself since I caught your post after the deadline, and I'm not
sure how helpful my info will be.
I had to do unit testing in winter semester. It was a small section of a
larger course and I had little time to play around with it. I accessed the
test output by clicking the mouse in the output window. Tab and shift tab, f6
and shift f6, and other standard keys availed me not. I was able to click the
mouse in the right spot because nvda reads what lies under the mouse pointer as
it moves. It was time consuming to get running, but I found that for each
session, the focus stayed in the output for test after test. If I restarted
visual studio or clicked the mouse to another area I would have to click back.
I wasn't happy about it, but there was no time to come up with an eligant
solution.
I had a similar problem designing universal windows binary apps. I can usually
access the front end code from solution explorer, but in universal windows
binary that didn't seem to be an option. In that case, I was able to set up a
custom keyboard shortcut in visual studio that let me switch between the
designer and the xaml code editor the way f6 and shift f6 would do in a perfect
world.
If there had been time, I would have attempted something similar for the unit
testing output.
Best,
Erik
On June 3, 2019 1:53:35 PM <jordyydeweer@xxxxxxxxx> wrote:
Hi Dante
No problem. A man needs some rest, from time to time.
No, I couldn’t find a solution… Maybe you do know one? 😉
Thank you in advance.
Kind regards
Jordy Deweer
[logo%20dewsystems%20(klein)]
info@xxxxxxxxxxxxx<mailto:info@xxxxxxxxxxxxx>
+32 473 39 27 50
www.dewsystems.be<http://www.dewsystems.be/>
Van: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> Namens
Dante Gagne (Redacted sender "danteg" for DMARC)
Verzonden: Monday, June 3, 2019 7:46 PM
Aan: program-l@xxxxxxxxxxxxx
Onderwerp: [program-l] Re: [URGENT] Unit Testing using Visual Studio
Jordy,
I’m sorry I didn’t get to this until now… I just got back from a week’s
vacation. I’m sorry I didn’t catch this until now.
Did you find a solution for your problem?
--Dante
From: program-l-bounce@xxxxxxxxxxxxx<mailto:program-l-bounce@xxxxxxxxxxxxx>
<program-l-bounce@xxxxxxxxxxxxx<mailto:program-l-bounce@xxxxxxxxxxxxx>> On
Behalf Of jordyydeweer@xxxxxxxxx<mailto:jordyydeweer@xxxxxxxxx>
Sent: Sunday, May 26, 2019 6:58 AM
To: program-l@xxxxxxxxxxxxx<mailto:program-l@xxxxxxxxxxxxx>
Subject: [program-l] [URGENT] Unit Testing using Visual Studio
Dear all
I try to run unit tests in Visual Studio 2019 and I see they run, but I cannot
see whether they succeeded or failed. How can I discover whether they did or
did not?
I also tried to use mstest from the command prompt, but there the tool says
that there are no tests to run… VS says there are eight…
Any quick help is extremely appreciated, since I am, honestly, in a hurry to
get this done… The deadline is tomorrow evening at 9 pm.
Thank you all so much for any assistance.
Warm greetings
Jordy Deweer
[logo%20dewsystems%20(klein)]
info@xxxxxxxxxxxxx<mailto:info@xxxxxxxxxxxxx>
+32 473 39 27 50
www.dewsystems.be<http://www.dewsystems.be/>