View Single Post

  #7  
Old 02-11-2019, 06:53 PM
mjr's Avatar
mjr mjr is offline
Area Manager
 
Join Date: Jan 2013
Location: 127.0.0.1
Posts: 1,048
Default

Nunavut...

What testing suite are you using? Unit Tests should run fast. Even if there are hundreds or thousands of them, they shouldn't time out your system.

Personally, if you're using a web page, you're probably doing it wrong. I know Visual Studio has built-in testing tools. And if you use NUnit, you can even create test cases for each test.

It also sounds like if they're using a deployment script, that the deployment script may need work. They should have a policy in place (I don't know why they don't) that if the tests don't pass, the code won't build (or something like that). And in that case, it should kick back to the dev team or project manager to let them know.

Unit tests should be small, fast, and have no conditional logic in them, except the "built-in" logic of the assert statements.
__________________
Skilled programmers aren't cheap. Cheap programmers aren't skilled.
Reply With Quote