What is SUT and where did it come from?

I see many people talking about the term SUT, but do not understand why they use that term.

SUT is what you want to test?

Where does this term come from and what does it mean?

For example in this test, what is my SUT?

[TestMethod]
public void UsersAction_should_return_IndexAction()
{
    const long id = 1;

    UsersViewModel viewModel = new UsersViewModel()开发者_如何学运维
    {
        SelectedUsers = new long[] { 1, 2, 3, 4 }
    };

    ActionResult result = _controller.Users(id, viewModel);

    result.AssertActionRedirect().ToAction("Index");
}

The System Under Test (SUT) from a Unit Testing perspective represents all of the actors (i.e one or more classes) in a test that are not mocks or stubs. In your example that would be the controller.

It most likely means "System Under Test", i.e. the system being tested, as opposed to other systems it may interact with, but which are not being explicitly tested (because they're someone else's responsibility).

Where does this term come from?

DUT (device under test) and UUT (unit under test) are very common abbreviations among test engineers (non-software test engineers). That's where the term SUT (system under test)
and CUT (code under test) ought to have come from.

Related:
2008 MSDN blog post Naming SUT Test Variables.

I've never heard the term either, but a quick search gave

System under test (SUT) refers to a system that is being tested for correct operation. [...] The term is used mostly in software testing.

A special case of a software system is an application which, when tested, is called an application under test.

The term SUT can also refer to a stage of maturity of the software because system testing is the successor of integration testing in the testing cycle.

From good old Wikipedia.

System Under Test SUT.

In your unit test example, if you really want to talk about SUT it's probably UsersAction. However, I have not come across anyone use SUT when talking about unit testing. To me this sounds more like something that would fit with integration/system/performance testing or alike.

For instance, take performance testing. Here you might say the SUT is the whole HW/SW system, or it might be just one of them depending on what you're testing in that specific performance test.

It is good to distinguish SUT and Test System.
The SUT can be part of the test system, illustrated in below picture: