iron-cms 0.2.1 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3dc16db2bf8c1ee5f0cca129113aed94f3064d405ae13b7a8a80cc2f601c4a4f
-  data.tar.gz: ff04983432ca9fce51945b29625144685b082047278f6afda51a057e70040b5a
+  metadata.gz: 0a723695ec8ae52789c95a89025f4b3581d5e132a8a1b15bc57303c420f42eed
+  data.tar.gz: 1af793ed846e38b642d94616dea5681e5199807efe28396ce67aba8b39faee4a
 SHA512:
-  metadata.gz: 8f1b195f43f04b198e29f18c8bae4dde22424dd869435db76c1e1ea644f8756e67ca0f0cd6f81b4b83410687c664e14952448b599125630c12a13dc547f744a8
-  data.tar.gz: c3c3fa9ae10cb698dac50abdac3f36fd6d0342f2ca7800e8d42445330fdb7863faab8a562b57d2d432a71e50ba7a12138d90592b77557a455e55a0899bfb5fba
+  metadata.gz: e5ecdb0c99b50e96bd357fb954119c443f6e2d1654adf2de467fd3f3e27d22b8d852bd65f7372ea61bfdab3e5ab87acdef6f22bed85d09289d9fcda8ffffdcb2
+  data.tar.gz: 2e9296551ecd8cfbd3229257fea50c69bf34f1a3df96bb915d370167fb0c98b6408b6caed649c600ada0b4bf6477b97055be420e4c76c4e810ab0d997ed9f6f6

data/README.md

@@ -9,6 +9,7 @@ Iron is a flexible CMS engine for Rails apps
 Iron CMS allows you to publish content types to your website. To set this up:
 
 1. **Install the pages controller** in your application:
+
    ```bash
    bin/rails g iron:pages
    ```
@@ -19,6 +20,7 @@ Iron CMS allows you to publish content types to your website. To set this up:
    - Create a default view template
 
 2. **Create custom templates** for your content types:
+
    ```bash
    bin/rails g iron:template article
    ```
@@ -60,6 +62,7 @@ Use `iron_picture_tag` for optimal image delivery:
 ```
 
 This automatically:
+
 - Generates responsive variants (150w, 320w, 640w, 1024w, 1920w)
 - Serves modern formats (AVIF, WebP) with automatic fallback
 - Adds proper dimensions to prevent layout shift
@@ -93,6 +96,38 @@ For cases where you need a basic responsive image without format optimization:
 
 This generates a standard `<img>` with srcset but without modern format variants.
 
+### Testing
+
+Iron provides test fixtures to populate your test database with CMS schema and content, eliminating the need to stub the SDK in your tests.
+
+#### Generating Fixtures
+
+Generate test fixtures from your development database (or production if you prefer):
+
+```bash
+bin/rails iron:fixtures:generate
+```
+
+This creates two files in `test/fixtures/iron/`:
+
+- `schema.tar.gz` - Content types, field definitions, and block definitions
+- `content.tar.gz` - All entries and their field data
+
+Regenerate these fixtures whenever you make changes to your CMS schema or content that you want reflected in tests.
+
+#### Using Fixtures in Tests
+
+Load the fixtures in your `test/test_helper.rb`:
+
+```ruby
+class ActiveSupport::TestCase
+  fixtures :all
+  Iron::TestFixtures.load
+end
+```
+
+The fixtures are loaded once at the start of your test suite. Rails' transactional tests provide test isolation by rolling back changes after each test.
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -174,6 +209,7 @@ To release a new version of the Iron gem:
    - Update `CHANGELOG.md` with the changes for the new version
 
 2. **Commit and tag the release:**
+
    ```bash
    git add -A
    git commit -m "chore: release version X.Y.Z"
@@ -181,11 +217,13 @@ To release a new version of the Iron gem:
    ```
 
 3. **Push to GitHub:**
+
    ```bash
    git push origin main --tags
    ```
 
 4. **Build and publish the gem:**
+
    ```bash
    gem build iron.gemspec
    gem push iron-X.Y.Z.gem