prototype for easy and declarative definition of Events that should be present in the EventStore during testing of something

100%

prototype for easy and declarative definition of Events that should be present in the EventStore during testing of something

✓ Published0🌍 Public

Last edited Feb 6, 2013

Created on Feb 6, 2013

This example shows a fluent C# API for declaratively defining expected events in an EventStore during testing. It uses a builder pattern with `InsertEventsTo(EventStore)` and chained `.AggregateId(...)` calls, mapping aggregate IDs to arrays of `FakeEvent` objects like `ContactCreated` and `TaskCreated`. The code highlights a readable, intention-revealing syntax for setting up test fixtures without explicit event construction logic.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 5001434

This example shows a debugging scenario for event sourcing, where two events with identical timestamps are replayed and returned in unpredictable order. The code displays two event objects—`UserCreatedEvent` and `UserCredentialsCreatedEvent`—with their UUIDs and aggregate root IDs, using JavaScript object literals. It illustrates the problem of sorting by `DateTime.Utc.Now` when fast-sequenced commands produce equal dates, leading to logical ordering failures. The example renders the raw event data and aggregates as plain text, relying on standard JavaScript syntax rather than any visualization library, focusing on the conceptual issue of timestamp collisions in EventStore queries.

RRestuta

60% match

Loading thumbnail…

Command to Event specification

This example demonstrates a command-to-event specification using the GoldMine CQRS framework, showing how a `CreateTaskCommand` sent through a `CommandBus` results in a single `TaskCreatedEvent`. The code relies on `Machine.Specifications` (MSpec) to define the behavioral test, using `Because` to trigger the command and `It` to assert that the `EventStore` contains exactly one matching event. It pairs `GoldMine.Core.Commands` and `GoldMine.Core.CommandHandlers` with an in-memory CQRS runtime, highlighting a test-driven verification of domain event generation. The rendering approach is purely code-based, with no visual output shown.

RRestuta

55% match

Loading thumbnail…

"New" test helper

This example demonstrates a test helper class named `New` that centralizes the creation of realistic `ContactDetails` objects for unit tests. The usage shows a test instantiating a `ContactCreatedEvent` with a fresh `Guid` and calling `New.ContactDetails()` to supply the required data. The `New` class is a static factory method that populates a `ContactDetails` instance with hardcoded values—including a birthday timestamp from `DateTime`, email, phone number, and a list of `StreetAddress` objects—using standard .NET collections and `List<T>`. The code relies on C# language features like the `var` keyword and inline object initializers, with no external libraries beyond the .NET framework.

RRestuta

54% match

Loading thumbnail…

JavaScript Object Builder

This example shows a JavaScript object builder pattern for generating test data, specifically constructing OrderModel instances through a fluent, chainable API. The code defines an `OrderModelBuilder` constructor that uses underscore.js utilities like `_.defaults` and `_.extend` to manage configuration and merge attributes for categories like paid tickets and states like sold-out. Methods such as `withPaidTicket()` and `withSoldOutState()` return new builder instances, while `build()` finalizes the object. It demonstrates the factory-style composition and reusable template for creating test fixtures in a testing or mock-data context.

GGolodhros

54% match

Loading thumbnail…

An eventing mechanism for Swift

This example demonstrates an eventing mechanism for Swift, showing how to create type-safe events with multiple handlers and automatic cleanup. It defines an `Event<T>` class that manages a collection of handler wrappers, allowing observers to subscribe and unsubscribe dynamically. The implementation uses the `Disposable` protocol for tear-down logic and the `Invocable` private protocol to abstract handler invocation, with `EventHandlerWrapper` holding a weak reference to the target to prevent retain cycles. The code highlights Swift’s protocol-oriented and generics features, as well as curried instance methods, to build a reusable notification system without relying on external libraries.

CColinEberhardt

53% match

Loading thumbnail…

BDD sintax example

This example demonstrates a Behavior-Driven Development (BDD) testing pattern in C#, showing how a tool's lifecycle is specified through a fluent, human-readable syntax. The code defines a `Feature` class with a `Scenario` method that uses the `_(...)` lambda operator to chain Given/When/Then steps, where each step executes a code block against a `Tool` object. The test asserts that after creation and use, the tool's `Look` property equals "used" via the `ShouldEqual` method. The visualization maps the relationship between the textual BDD steps and their corresponding executable actions, highlighting the structure of the specification.

RRestuta

47% match

Loading thumbnail…

Gist db8c3f8fda7a4d6857a10214268a0047

This example demonstrates a JSON schema that defines the structure of a calendar event, specifying properties such as start and end dates, summary, location, and description. It shows the required fields and data formats needed to represent an event, likely for use in a scheduling or event-management interface. The schema itself is the core artifact, using standard JSON Schema draft 2020-12 conventions. No external visualization libraries are employed; the example focuses purely on the data contract. The rendering approach is not depicted, as the code provides only the schema definition.

MMoritzStefaner

47% match

Loading thumbnail…

Gist 7026512

This example demonstrates object-oriented JavaScript patterns for modeling zoo animals, showing how constructor functions and prototypes create shared behavior. The code defines an `Animal` constructor with `identify()` and `name()` methods on its prototype, while a `Zoo` object manages collections of animals. Although the zoo methods contain incomplete logic, the driver code tests animal identification, leg counts, and prototype method sharing across instances. The example uses plain JavaScript—no external libraries—relying on `console.log` for output and a custom `assert` function for validation. It illustrates inheritance and code reuse, though the zoo aggregation methods remain non-functional as written.

EElaineYu

46% match