Skip to content

Commit a66770a

Browse files
committed
spec: use an unregistrable rababa config name
The sweep's load path brings the monorepo's rababa-configs into scope, where a "default" config genuinely exists — the missing-config error never fires. A name that cannot be registered keeps the spec's precondition environment-independent.
1 parent b55a355 commit a66770a

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

‎spec/stdlib_functions_spec.rb‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,11 @@
5656

5757
describe ".rababa (without registered config)" do
5858
it "raises ExternalUtilError naming the missing config" do
59-
expect { described_class.rababa("كتب", config: "default") }.to raise_error(
59+
# A name that cannot be registered: the sweep's load path puts the
60+
# monorepo's rababa-configs in scope, where "default" exists.
61+
expect { described_class.rababa("كتب", config: "no-such-config") }.to raise_error(
6062
Interscript::ExternalUtilError,
61-
/No rababa config registered under 'default'/
63+
/No rababa config registered under 'no-such-config'/
6264
)
6365
end
6466
end

0 commit comments

Comments
 (0)