Unit Testing - Definitions

Like everything that understands words, it is much easier to learn a language. Can anyone listen to all the words used in unit testing with their definitions (e.g. Mock, Fixture, etc.).

+4
definition unit-testing architecture
Mar 11 '09 at 1:58
source share
4 answers

It looks like a great page: http://xunitpatterns.com/Glossary.html

It includes:

  • SUT
  • synchronous test
  • A task
  • TDD
  • test automater
  • test case
  • test code
  • check condition
  • test context
  • test database
  • testing arrears
  • test driver
  • driving test
  • test error
  • Testing error
  • test fixture
  • test fixture
  • test fixture
  • test package
  • test reader
  • test result
  • test run
  • test smell
  • test stripper
  • Test success
  • test suite
  • testing error correction
  • test development
  • test development
  • test latest development
  • test match
  • test

Regarding ridicule, etc. this might be useful:

This table and its links may be more useful:

http://xunitpatterns.com/Mocks,%20Fakes,%20Stubs%20and%20Dummies.html

+2
Mar 11 '09 at 2:10
source share

Perhaps these articles will become more useful:

Wikipedia:

In computer programming, unit testing is a method of developing and developing software in which the programmer gains confidence that individual units of source code are suitable for use. The unit is the smallest verifiable part of the application. In procedural programming, a unit can be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method that can belong to a base / superclass, an abstract class, or a derived / child class.

Unit testing can be done using something as simple as moving the code to the debugger; modern applications include using a test environment such as xUnit.

Ideally, each test case is independent of the others; Double objects such as plugs, false or fake objects 1 , as well as test harnesses can be used to isolate the modules separately. Unit testing is usually performed by software developers to ensure that code written by other developers complies with the software requirements and behaves as the developer intended.

MSDN:

The main goal of unit testing is to take the smallest part of the software under test in the application, isolate it from the rest of the code and determine whether it will behave exactly as you expect. Each block is tested separately before integrating them into modules to test interfaces between modules. Unit testing has proved its worth in the fact that during its use a large percentage of defects were detected.

Extreme rules:

Unit tests allow you to create collective code. When you create unit tests, you protect your functionality from accidental damage. The requirement that all code pass all unit tests before its release ensures that all functions will always work. Code ownership is not required if all classes are protected by unit tests.

+2
Mar 11 '09 at 2:00
source share

I also found a glossary of test conditions , but it does not define Mock or Fixture, but it is possible to add new ones. Once the question is satisfied with your satisfaction, perhaps this can become a canonical source.

0
Mar 11 '09 at 2:05
source share

Mock

P.

  • A type of tortoise used mainly in soup.
  • The code construct used in unit testing, named after No. 1. The layout looks like the real thing for the tested code, however, any attempts to interact with it lead only to sad songs.

v.

  • To build a layout for use in testing.
0
Mar 11 '09 at 2:18
source share



All Articles