Help us understand the problem. What is going on with this article?

xUnit Test Patterns ユニットテストの不吉な臭い

はじめに

xUnit Test Patterns: Refactoring Test Codeにあるユニットテストの不吉な臭いから抜粋。

テストコードの不吉な臭い(Code Smells)

  1. 条件付きのテストコード(Conditional Test Logic)
  2. テストを書くのが困難なコード(Hard-to-Test Code)
  3. テストコードの重複(Test Code Duplication)
  4. 製品コードにテストコードがある(Test Logic in Production)

振る舞いの不吉な臭い(Behavior Smells)

  1. アサート文がランダムに実行される(Assertion Roulette)
  2. テストが不規則に実行される(Assertion Roulette)
  3. 壊れやすいテスト(Fragile Test)
  4. 何らかの機会にデバッグが必要。(Frequent Debugging)
  5. テストの実行に手動の介入が必要(Manual Intervention)
  6. 遅いテスト(Slow Tests)

プロジェクトの不吉な臭い(Project Smells)

  1. バグだらけのテスト(Buggy Tests)
  2. 開発者がテストコードを書かない(Developers Not Writing Tests)
  3. テストコードの保守コストが高い(High Test Maintenance Cost)
  4. 製品のバグ(Production Bugs)
Why do not you register as a user and use Qiita more conveniently?
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
Comments
Sign up for free and join this conversation.
If you already have a Qiita account
Why do not you register as a user and use Qiita more conveniently?
You need to log in to use this function. Qiita can be used more conveniently after logging in.
You seem to be reading articles frequently this month. Qiita can be used more conveniently after logging in.
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away