# Best Practice

# How to use checkpoints

Header graphic

# Checkpoints

[Checkpoints copy goes here]

# Library checkpoints

You might find yourself writing the same steps over and over again in new goals in the same project. Library checkpoints allow you to save these common sequences and reuse them whenever and wherever you like.

Like shared checkpoints, library checkpoints can be imported at any point in your journey. Unlike shared checkpoints, they're not limited to a single-use in each journey, and they're instead shared across your entire project.

# WARNING

Unlike shared and regular checkpoints, library checkpoints exist outside of the current version control system. Once a library checkpoint is changed, new executions of previous journey versions will also use the new library checkpoint version.

Library checkpoints are really useful if you have your tests organized into multiple goals. This centralizes your maintenance instead of requiring you to manually copy changes between goals. You, therefore, get absolute reusability.