Skip to content

Test startegy #11

Open
Open
@darkl

Description

@darkl

Ok - we have a slow implementation of the GraphClimber (no Reflection.Emit/Expressions here).

This allows us to play with the api (and apply changes to it), and also allows us to do a bit TDD: we can write integration tests for the SlowGraphClimber. After that, when we implement the real GraphClimber, we run the tests and find bugs.

Since GraphClimber can only be tested by integration tests, I suggest we write some simple processors and check that they behave correctly. Some processors include: finding all paths in an object with a null value, extracting all strings of an object, some simple serializer/deserializer and etc.

I'd like hear about other ideas for processors/tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions