Skip to content

Proves the at-rest test's UPDATE assertion #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johnnyt merged 1 commit into from
Oct 11, 2026
Merged

Proves the at-rest test's UPDATE assertion #267

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions test/statifier_persistence/ecto/position_blob_at_rest_test.exs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,11 @@ defmodule StatifierPersistence.Ecto.PositionBlobAtRestTest do
# custom-type clause answered `[name, :binary]` -> red on the first
# assertion: the INSERT bound the location in the clear. Verified red,
# reverted.
# sabotage (the UPDATE path alone): in Storage.Ecto.update_execution/2,
# dropped `position_blob` from the `set:` list and set it through a
# query `update` with `type(^blob, :binary)` -> the INSERT assertions
# pass and the refute on `updates` goes red: the step's UPDATE bound the
# raw position carrying the location. Verified red, reverted.
test "an encrypting :blob_type keeps the location out of the stored column and the bound blob",
%{machine: machine, chart_blob: chart_blob, stamps: stamps} do
{:ok, store} = Storage.new(Storage.Ecto, persistence: BlobTyped)
Expand Down
Loading