Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 7
    strictly speaking this sounds like an integration or system test not a unit test Commented Oct 2, 2013 at 8:47
  • That may be correct, I don't really know what this kind of test is called. I assumed unit test, because it doesn't matter where the project is deployed, the front-end is a functionality that should always be there... Commented Oct 2, 2013 at 8:58
  • After reading up the definition, I don't think this is a integration/system test. I'm explicitly testing the "frontend" unit, it just happens on a deployed platform... I think. Commented Oct 2, 2013 at 9:00
  • well you know the code so you are best placed to say, but from the description it sounds like you are testing more than one thing, which either means you are testing more than one unit or you are breaking the SRP Commented Oct 2, 2013 at 10:00
  • 1
    I would call this a UI/interface test. Depending on exactly what you are testing, can be an automated acceptance or functional test. Commented Oct 2, 2013 at 14:48