Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Integration tests

Integration tests

Scheduled Pinned Locked Moved C#
helpdesigndockertestingquestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U Offline
    U Offline
    User 4483848
    wrote on last edited by
    #1

    Are integration tests worth the trouble? I personally don't like integration tests, or at least not when they're mixed in with unit tests. They are much more costly than unit tests and their benefit seems to be minimal. There was a time when I had to write lots of them for legacy code. They were complicated, took ages to write, forever breaking, very hard to fix and took ages to run. As far as I can see, if you have good unit tests, then the only real benefit is verifying that the IoC container is configured correctly and the config is passed through correctly. All of these things will get picked up by minimal manual or automated UI tests anyway. The time they take to execute is a bit of an issue for. I like to do TDD and like to run all tests after most changes. This isn't practical with Integration tests as they take too long to execute, so I then need to find the test(s) I want to execute and choose those instead of just using a keyboard shortcut. Does anybody know a good way of separating them? Does anybody know a better place for doing these kind of tests ie. no in MSTest or NUnit?

    A 1 Reply Last reply
    0
    • U User 4483848

      Are integration tests worth the trouble? I personally don't like integration tests, or at least not when they're mixed in with unit tests. They are much more costly than unit tests and their benefit seems to be minimal. There was a time when I had to write lots of them for legacy code. They were complicated, took ages to write, forever breaking, very hard to fix and took ages to run. As far as I can see, if you have good unit tests, then the only real benefit is verifying that the IoC container is configured correctly and the config is passed through correctly. All of these things will get picked up by minimal manual or automated UI tests anyway. The time they take to execute is a bit of an issue for. I like to do TDD and like to run all tests after most changes. This isn't practical with Integration tests as they take too long to execute, so I then need to find the test(s) I want to execute and choose those instead of just using a keyboard shortcut. Does anybody know a good way of separating them? Does anybody know a better place for doing these kind of tests ie. no in MSTest or NUnit?

      A Offline
      A Offline
      Abhinav S
      wrote on last edited by
      #2

      There are a number of other tools. Pros and cons, you could analyze yourself. E.g. http://xunit.codeplex.com/wikipage?title=Comparisons[^].

      Apps - Color Analyzer | Arctic | XKCD | Sound Meter | Speed Dial

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups