List view
- No due date•5/5 issues closed
- No due date•11/11 issues closed
- No due date•3/3 issues closed
- No due date•4/4 issues closed
- No due date•2/2 issues closed
- No due date•2/2 issues closed
- No due date•2/2 issues closed
- No due date•5/5 issues closed
- No due date•2/2 issues closed
- No due date•2/2 issues closed
- No due date•2/2 issues closed
- No due date•1/1 issues closed
- No due date•5/5 issues closed
- No due date•1/1 issues closed
- No due date•4/4 issues closed
Several other transformative features should be sensitive to a possible type mapping choice made with AutoMapper; if an explicit map exists from serialized to non-serialized form, the map should be used. This makes AutoMapper a fairly central piece of Patterns, and it needs to be imported. DoD: AutoMapper has been introduced in Patterns via the new IMappingServices interface (aggregates IMappingEngine, IConfiguration, and IConfigurationProvider using a DI model), and in Patterns.Autofac via the new MappingModule (which registers all 4 services with Autofac).
No due date•2/2 issues closedIt's time for the old Patterns Reflection-based code to start getting integrated. DoD: 1. First needed feature (property scanning) is implemented 2. All features are implemented following BDD workflow 3. All documentation is present, including gists
No due date•1/1 issues closedDoD: the following API's have been fully documented in the wiki, with code samples: 1. Autofac RunTime and Configuration modules 2. ICollection.AddRange 3. IEnumerable.Each 4. IConfigurationSource 5. Try.Get, Try.Do, Try.HandleErrors.DefaultStrategy 6. ILog injection, LoggingInterceptor 7. IDateTimeInfo 8. CompiledRegex
No due date•11/11 issues closedA CI server needs to be built, and a build and test report viewer needs to be made publicly available. DoD: 1. Notifications 2. Build reporting 3. Feature and Scenario reporting 4. Code coverage reporting
No due date•2/2 issues closedStep definitions are more-or-less scoped to individual roles and responsibilities within the test domain. Domain objects under test are typically wrapped in "context" objects that are injected into step definition constructors, thus taking advantage of automatic state tracking via SpecFlow's automatic DI. DoD: All scenarios are bound to OOP, DI-centric step definitions
No due date•11/11 issues closedDOD: Patterns.Logging and Patterns.Autofac.Logging namespaces with optimal (TBD) coverage. Features: 1. Automatic injection of ILog constructor dependencies (with properly type-bound instances) 2. IInterceptor implementation using Common.Logging 3. Configurable module 4. Registration helpers
No due date•6/6 issues closedDoD: BDD workflow retrofitted to existing code. Refactors may be necessary. "First-class citizen" coverage target is 100%. Wrapper coverage is insignificant. Must include IoC scenarios.
No due date•9/9 issues closedavoid "access to modified closure" issues by providing overloads of Get and Do that correspond with the variations of Func and Action
No due date•2/2 issues closed