jobpayload 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: a6a279c0d7d4f97b7ba76677146e0d73ebd7b65df8db221b93b61a6e69e1d30a
+  data.tar.gz: 4dc6bc66b1296cf30bf03e1ebad5d68797868f6cfc84117edc9246b555a63881
+SHA512:
+  metadata.gz: e7b0ffe7184e08ca69623c383dd9ebb4f323408ea7a343d3a31accb0c310009c672e00af66411e78583d66545780c326956f098ce70ce86315fef4f1b3f9d10e
+  data.tar.gz: 2dba7bc4c7dbb0786367ae438d94accedf7312f99f9c3733dfc7a3845f2fcf6153e72d260edcfca8fb486fb62f15327fe2008a44bfa9a3f6fe5c50fdf726e093

data/CHANGELOG.md

@@ -0,0 +1,52 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+## 0.1.0
+
+Initial release. The single question v0.1.0 answers is: *can the current
+application deserialize this previously serialized Active Job payload?*
+
+### Added
+
+- `jobpayload snapshot`: evaluates snapshot cases declared with
+  `JobPayload.define { fixture "name" { SomeJob.new(...) } }` and writes one
+  JSON fixture per case from `ActiveJob::Base#serialize`.
+  - Fixture schema v1 (`jobpayload_schema: 1`) with `name`, `source` versions and the
+    serialized `job` hash.
+  - Volatile metadata (`job_id`, `provider_job_id`, `enqueued_at`, `executions`,
+    `exception_executions`, non-nil `scheduled_at`) is normalized to fixed values;
+    custom keys added by a job's own `#serialize` are kept.
+  - Byte-for-byte deterministic output: recursively sorted keys, fixed
+    two-space layout independent of the json gem version, UTF-8, LF, final newline,
+    atomic writes, fixtures processed in name order.
+  - Existing fixtures are never overwritten unless `--update` is given.
+- `jobpayload check`: boots the application once and, for every fixture, runs
+  `ActiveJob::Base.deserialize` and `ActiveJob::Arguments.deserialize` on fresh
+  copies of the payload. Jobs are never performed, enqueued or retried.
+- Stable finding codes: `AJP001` fixture_invalid, `AJP101` unknown_job_class,
+  `AJP102` job_deserialize_failed, `AJP201` argument_deserialize_failed,
+  `AJP202` globalid_record_missing (inconclusive), `AJP900` environment_error.
+- GlobalID records missing from the test database are reported as inconclusive
+  (exit 0 by default, exit 1 with `--fail-on-inconclusive`). `AJP202` is only
+  used when the failing argument is an Active Job GlobalID reference
+  (`{"_aj_globalid": ...}`) and a record-missing exception is in the cause chain;
+  any other argument failure is `AJP201`, even when `RecordNotFound` appears in
+  the cause chain (for example a custom serializer's `find_by!`).
+- Exception classification by class and cause chain (cycle-safe), not by message text.
+- Failing argument location (`arguments[1]`, `arguments[0]["batch"][1]`, ...); every
+  failing argument gets its own finding, so an inconclusive missing record cannot
+  hide a breaking argument next to it.
+- Text output and JSON output schema v1; `--debug` adds backtraces to text output.
+  JSON vocabulary: top-level `status` is `pass` / `fail` / `tool_error`; fixture
+  `status` is `pass` / `fail` / `inconclusive` / `tool_error`; finding `severity`
+  is `error` (compatibility break) / `warning` (inconclusive) / `fatal`
+  (tool/environment failure); `summary` counts `compatible`, `incompatible`,
+  `inconclusive` and `tool_errors`. Exception messages, fixture file names and
+  paths are always emitted as valid UTF-8.
+- Exit codes: 0 compatible, 1 compatibility failure, 2 usage/configuration/boot/tool error.
+- Options: `--boot`, `--environment` (default `test`), `--cases`, `--output`,
+  `--fixtures`, `--update`, `--format text|json`, `--fail-on-inconclusive`, `--debug`.
+- `require "jobpayload"` does not load Active Job; Active Job (and the json
+  library) is only loaded after the host application has booted.
+- Supported: Ruby 3.3, 3.4, 4.0 with Active Job 7.2, 8.0, 8.1.

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 cottondesu
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.