Objective-C iOS Development for Legacy & Enterprise Apps · レッスン

Objective-CのユニットテストとUIテスト

XCTestで効果的なユニットテストを記述し、Objective-Cアプリケーションの安定性と正確性を確保するUIテストを作成します。

「Objective-CのユニットテストとUIテスト」はCoddyKit上の無料Objective-C iOS Development for Legacy & Enterprise Appsレッスンです。これはレッスン2/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはObjective-C iOS Development for Legacy & Enterprise Apps学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Objective-C iOS Development for Legacy & Enterprise Appsコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Welcome to Testing!

In the world of enterprise iOS development, reliable applications are non-negotiable. This lesson introduces you to the essential practices of testing in Objective-C.

You'll learn how to write unit tests for small code components and UI tests to simulate user interactions, ensuring your apps are robust and error-free.

Meet XCTest

Apple provides a powerful testing framework called XCTest, built right into Xcode. It's the native way to write tests for your iOS, macOS, watchOS, and tvOS applications.

Integrated: Seamlessly works with Xcode's build and debug tools.
Flexible: Supports both low-level unit tests and high-level UI tests.
Powerful: Provides a rich set of assertion macros to verify code behavior.

Unit Tests: The Basics

Unit tests focus on testing the smallest possible units of code in isolation, like a single method or function. Their goal is to ensure each part of your code works exactly as expected.

They are typically fast to run and help catch bugs early in the development cycle, making your codebase more stable and easier to maintain.

Setting Up Unit Tests

To add unit tests to your Xcode project, you'll typically add a new Unit Test Bundle target. Xcode then sets up a dedicated target for your test files.

Your test files will import the XCTest framework and your application's code, allowing you to write tests against your app's classes and methods.

Your First Unit Test

Let's write a simple unit test for a basic calculator method. We'll create a MyCalculator class and then a test class to verify its addition method.

// MyCalculator.h (Class to be tested)
#import <Foundation/Foundation.h>
@interface MyCalculator : NSObject
- (NSInteger)addNumber:(NSInteger)num1 toNumber:(NSInteger)num2;
@end

// MyCalculator.m
#import "MyCalculator.h"
@implementation MyCalculator
- (NSInteger)addNumber:(NSInteger)num1 toNumber:(NSInteger)num2 {
  return num1 + num2;
}
@end

// MyCalculatorTests.m (Example Test File)
#import <XCTest/XCTest.h>
#import "MyCalculator.h" // Import class to test

@interface MyCalculatorTests : XCTestCase
@end

@implementation MyCalculatorTests

- (void)testAdditionOfTwoNumbers {
  MyCalculator *calculator = [[MyCalculator alloc] init];
  NSInteger result = [calculator addNumber:5 toNumber:3];
  // XCTAssertEqual checks if two values are equal
  XCTAssertEqual(result, 8, @"Addition of 5 and 3 should be 8.");
}

- (void)testAdditionWithNegativeNumbers {
  MyCalculator *calculator = [[MyCalculator alloc] init];
  NSInteger result = [calculator addNumber:-5 toNumber:2];
  XCTAssertEqual(result, -3, @"Addition of -5 and 2 should be -3.");
}

@end

XCTAssert: Check Your Work

XCTest provides a variety of assertion macros to verify conditions in your tests. If an assertion fails, the test fails, indicating a bug or unexpected behavior.

XCTAssertEqual(a, b, format...): Checks if a equals b.
XCTAssertTrue(condition, format...): Checks if condition is true.
XCTAssertNil(expression, format...): Checks if expression is nil.
XCTAssertNotNil(expression, format...): Checks if expression is not nil.

UI Tests: User's View

While unit tests check internal logic, UI tests verify that your app's user interface behaves correctly from a user's perspective. They simulate taps, swipes, text input, and other interactions.

UI tests are slower than unit tests because they launch the entire application, but they are crucial for catching issues related to the app's overall flow and user experience.

Setting Up UI Tests

Similar to unit tests, you add UI Test Bundle targets to your Xcode project. This creates a separate target specifically for your UI test files.

UI tests interact with your app through the XCUIApplication class, which represents your running application and allows you to find and interact with UI elements.

Xcode UI Test Recorder

Xcode offers a helpful UI Test Recorder that can automatically generate UI test code as you interact with your app. You launch your app in a special mode, perform actions, and Xcode writes the corresponding XCTest code.

This recorder can be a great starting point for new UI tests, which you can then refine and expand manually.

Your First UI Test

Let's create a UI test that launches an app, taps a button, and then verifies that a label on the screen updates as expected.

Note: UI elements need accessibility identifiers or labels for easy lookup.

// MyAppUITests.m (Example UI Test File)
#import <XCTest/XCTest.h>

@interface MyAppUITests : XCTestCase
@end

@implementation MyAppUITests

- (void)testButtonTapUpdatesLabel {
  // 1. Launch the application
  XCUIApplication *app = [[XCUIApplication alloc] init];
  [app launch];

  // 2. Find the button using its accessibility identifier and tap it
  // (Assume a button with accessibility ID "MyButtonIdentifier" exists)
  XCUIElement *myButton = app.buttons[@"MyButtonIdentifier"];
  [myButton tap];

  // 3. Find the label and assert its new value
  // (Assume a static text label with accessibility ID "MyLabelIdentifier" exists)
  XCUIElement *myLabel = app.staticTexts[@"MyLabelIdentifier"];
  XCTAssertTrue([myLabel.label containsString:@"Tapped!"],
                @"Label should show 'Tapped!' after button tap.");
}

@end

Test Your Knowledge

Let's check your understanding of Objective-C testing.

Recap: Test with Confidence

You've taken a crucial step towards building more reliable Objective-C applications!

We explored XCTest, Apple's native testing framework.
You learned about unit tests for isolated code logic and wrote your first example.
We covered UI tests for simulating user interactions and saw how to verify UI behavior.

Embracing testing makes your apps more stable, maintainable, and ultimately, more successful.

よくある質問

「Objective-CのユニットテストとUIテスト」レッスンは無料ですか？

はい。「Objective-CのユニットテストとUIテスト」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Objective-C iOS Development for Legacy & Enterprise Appsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Objective-C iOS Development for Legacy & Enterprise Appsコースには全4レッスンが含まれています。

「Objective-CのユニットテストとUIテスト」で何を学びますか？

XCTestで効果的なユニットテストを記述し、Objective-Cアプリケーションの安定性と正確性を確保するUIテストを作成します。ブラウザで直接実行するハンズオンコードでObjective-C iOS Development for Legacy & Enterprise Appsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Objective-C iOS Development for Legacy & Enterprise Appsを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのObjective-C iOS Development for Legacy & Enterprise Appsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン2/4です。

「Objective-CのユニットテストとUIテスト」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このObjective-C iOS Development for Legacy & Enterprise Appsレッスンでコードを書いて実行できますか？

はい。すべてのObjective-C iOS Development for Legacy & Enterprise Appsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Objective-C iOS Development for Legacy & Enterprise Appsに戻る