#good programming practice

[arifinfrds-blog]

In this speed coding session, we write unit tests for a Swift ViewModel built with the MVVM architecture and powered by Combine and @MainActor concurrency. You’ll see how to: ✅ Write precise and meaningful unit tests using XCTest 🔍 Test async @MainActor functions with Combine’s @Published properties 🧪 Mock dependencies like ChinesePhraseSaver, Loader, and Deleter 🔄 Validate onLoad() and onTapFavorite() logic ⚠️ Handle error states with shouldShowErrorAlert 🧼 Ensure correctness using behavior-driven test naming We aim for properly crafted unit tests that naturally lead to high code coverage, making your codebase more robust and regression-proof. 🎯 Difficulty: Intermediate to Advanced

View On WordPress

[arifinfrds-blog]

Maintaining fast unit test feedback is crucial as an app and team grow over time. Without proper modularization, unit testing can become painfully slow. By structuring code into independent modules and utilizing macOS-based testing strategies, we can drastically improve test execution speed. This results in faster development, quicker bug fixes, and a smoother engineering experience. If you’re working on a growing iOS project, now is the time to start modularizing. Not only will it save you time today, but it will keep your project maintainable and efficient as your team and codebase scale. Start with one module, test the benefits, and see the difference! 🚀

View On WordPress

[arifinfrds-blog]

The Dependency Inversion Principle (DIP) is a fundamental concept in software development that helps create flexible and maintainable code. In this article, I'll explore its history, the problem of tight coupling, and different approaches to applying DIP in Swift.

Dependency Inversion Principle (DIP) in iOS Swift

[arifinfrds-blog]

Understanding the Liskov Substitution Principle (LSP) in Swift

In this article, we'll explore how Liskov Subtitution Principle (LSP) works in Swift with practical examples, including a mock implementation for testing and a real implementation that loads data remotely. We will also discuss common pitfalls and best practices for ensuring LSP compliance in your Swift applications.

The Liskov Substitution Principle (LSP) is one of the five SOLID principles of object-oriented design. It states that: “Objects of a superclass should be replaceable with objects of a subclass without affecting the correctness of the program.” (Paraphrased from Barbara Liskov’s) Barbara Liskov, a pioneering computer scientist, introduced this principle in 1987 as part of her research on data…

Understanding the Liskov Substitution Principle (LSP) in Swift

[arifinfrds-blog]

Open/Closed Principle (OCP) in Swift using Decorator Pattern

The Open/Closed Principle (OCP) is one of the fundamental principles of object-oriented design, forming part of the SOLID principles. The concept is simple: “Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification.” This principle encourages building systems where new functionality can be added without altering existing code. This leads to more maintainable, scalable, and robust software. In this article, we will explore the Open/Closed Principle and how to apply it in Swift through examples, focusing on the Decorator Pattern to extend behavior without modifying the original code.

SOLID: Open Close Principle Overview The Open/Closed Principle (OCP) is one of the fundamental principles of object-oriented design, forming part of the SOLID principles. The concept is simple: “Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification.” This principle encourages building systems where new functionality can be added without…

Open/Closed Principle (OCP) in Swift using Decorator Pattern

[arifinfrds-blog]

SOLID : Single Responsibility Principle (SRP)

The Single Responsibility Principle (SRP) is one of the SOLID principles in software design. Checkout the SRP explained in this articl

What is SRP? The Single Responsibility Principle (SRP) is one of the SOLID principles in software design. It states that a component should have only one reason to change. In other words, a class, struct, or any components, should have a single purpose and should not be modified for multiple reasons. Consider the following Swift struct: struct RemotePhrase: Decodable { let chinese: String let…

SOLID : Single Responsibility Principle (SRP)

[arifinfrds-blog]

Clean Architecture: A Blueprint for Scalable and Maintainable Software

Clean Architecture is a design approach for building flexible, maintainable, and testable apps by keeping concerns separate and well-defined. Let's deep dive in in this article!

Clean Architecture is a software design philosophy that helps developers build flexible, maintainable, testable, and scalable applications. It emphasizes separation of concerns, ensuring that different parts of the application have clear responsibilities and do not mix unrelated logic. Think of it like designing a beautiful city with a well-planned infrastructure—roads, districts, utilities, and…

Clean Architecture: A Blueprint for Scalable and Maintainable Software

[arifinfrds-blog]

Understanding the Decorator Pattern in Swift: A Practical Example

Overview Design patterns are a cornerstone of software development, providing reusable solutions to common problems. The Decorator Pattern is a structural design pattern that allows you to dynamically add new behavior to objects without altering their structure. It follows the Open/Closed Principle, which states that a class should be open for extension but closed for modification. In this…

Understanding the Decorator Pattern in Swift: A Practical Example