Writing Cleaner Test with Domain-Specific Assertions
Domain-specific assertions can help create an extremely clean test base. Learn how to create your own manually or with LLM.
Tag: clean-code
-
-
Create In-Memory Repository based on HashMap for Unit Tests Using Generative AI Instead of Mocking
Increasing accuracy of your Unit Tests and making them as easy to write as Integration Tests.
-
Decoupling DTOs from Service Layers in Transactional Systems
Efficient strategies for managing data transformation within Spring Boot and RDBMS environments, optimizing response handling and maintaining transactional integrity.
-
Crafting Unique ID from Composite Attributes for Key-Value Pairs (Redis, Map, and even Droppable-Id in React Beautiful DnD)
Guidelines for generating clean, unique ID fields from composite attributes to enhance application maintainability and scalability, using encapsulated functions and semantically meaningful IDs.
-
![Naming Convention for Indexes [Quick Read]](/images/naming-contention-database-redux-indexes.png)
Naming Convention for Indexes [Quick Read]
Create a clean descriptive index name
-
How to generate and enforce naming conventions for you and your team?
Creating a good naming convention that can help you and your team maintain a clean codebase
-
6 Approaches to come up with good variables, methods, and class names to create a fluent codebase
Easy approaches to help you come up with descriptive clean names
-
3 Important Benefits of Good Naming in Programming / Software
The Naming convention is more important than any other part of clean code. Once you nail the name, everything else fits precisely!
-
How we implemented OData for MongoDB and use it in OpenAPI
Implementing OData, Utilizing Specifications, and Enhancing API Flexibility.
-
-
Separating Connectors and Service (Business Logic) - A Key Principle for Service Reusability
Separating connectors from business logic in a service-oriented architecture promotes reusability and single responsibility.
-
Pre-save Data Validation
Data validation at various stages minimizes bugs and unnecessary overhead, ensuring consistent and accurate information flow.
-
Writing Meaningful Log Messages
Placeholder
-
JUnit Template For Tracking Bugs in Unit Tests
Placeholder
-
Separate Technical Code From Domain Code in both Frontend and Backend
Separate out technical code from business/domain logic for extreme reusability for code.
-
Code Reviews and Pair Programming
Placeholder
-
Enforcing Architecture with Architecture Testing
Architecture is a crucial pillar of accelerating product delivery. It's hard to keep a team in sync with architecture over time. Architectural testing can enforce architectural decisions as simple tests, dramatically reducing code review effort and extending code maintainability.
-
Mutation Testing
Placeholder
-
Leave Clues
Comments and Naming Conventions
-
-
Writing better commits with Atomic Commits
Why small frequent commits leads to higher productivity
-
-
Writing cleaner tests with creative variable names
Creative variable names in tests can make them fun and interesting to read.
-
Making TDD and Testing easier
Placeholder
-
Writing better commit with conventional commits
Placeholder
-
Writing cleaner tests with Fluent Assertions
Fluent Assertions make tests highly readable and English-like, presenting a concise structure that simplifies comprehension
-
Writing cleaner tests with Test Data Factories
Consolidating object creation, mock of methods and more.
-
Make your code configurable.
Things that should take 0 coding effort
-
Debugging Effectively
Placeholder
-
Thinking and writing cleaner tests with method/when/should blocks
A template for thinking and creating understandable uniform tests
-
Clean code - Naming convension for design patterns
Making it easy for future-code readers to understand
-
Maintaining Documentation
Placeholder
-
-
How we created a query and evaluation language similar to Google Sheets and Excel formulas
Using the best current programming language creation-tool.
-
Clean Code Resources and Tools
Constructing the simplest possible code
-
Leave it better than you found it
Atomic Habits applied to code. Thanks James Clear.
-
Exception handling
and Logging with style
-
Remove un-necessary code
You ain’t gonna need it
-
Avoid inventing algorithms and data structures
especially for maths
-
Avoid creating god classes and long methods
Minimalism
-
Make the database do the heavy lifting
You cannot compete with SQL
-
Flat is better than nested
Leave when not okay
-
Clean Code
constructing the simplest possible code that would solve your problem resulting in an increase in productivity by producing higher quality in less time.