Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / nspec/NSpec issues and pull requests
#154 - Docs: move readme Additional info to website
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 1 comment
#154 - Docs: move readme Additional info to website
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 1 comment
#153 - Docs: show nuget and appveyor badges in readme
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
#153 - Docs: show nuget and appveyor badges in readme
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
#152 - Chore: AppVeyor CI build does not trigger when tagging commit
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 3 comments
#151 - Provide instructions/sample to create console test application
Issue -
State: open - Opened by BrainCrumbz about 8 years ago
Labels: docs/website, enhancement
#151 - Provide instructions/sample to create console test application
Issue -
State: open - Opened by BrainCrumbz about 8 years ago
Labels: docs/website, enhancement
#150 - Packages: don't ship NSpecRunner on .NET Core targets
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
#149 - chore(package): create branch to test appveyor PR trigger
Pull Request -
State: closed - Opened by BrainCrumbz about 8 years ago
#149 - chore(package): create branch to test appveyor PR trigger
Pull Request -
State: closed - Opened by BrainCrumbz about 8 years ago
#148 - chore(package): build dotnet-test-nspec package
Pull Request -
State: closed - Opened by BrainCrumbz about 8 years ago
#148 - chore(package): build dotnet-test-nspec package
Pull Request -
State: closed - Opened by BrainCrumbz about 8 years ago
#147 - Restore repository after forced push
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 2 comments
#147 - Restore repository after forced push
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 2 comments
#146 - Question: Is there a way to get code coverage tools to recognize NSpecs specs?
Issue -
State: closed - Opened by danielterabyte about 8 years ago
- 16 comments
#146 - Question: Is there a way to get code coverage tools to recognize NSpecs specs?
Issue -
State: closed - Opened by danielterabyte about 8 years ago
- 16 comments
#145 - Fix NSpec package to work after .NET Core porting
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 4 comments
#145 - Fix NSpec package to work after .NET Core porting
Issue -
State: closed - Opened by BrainCrumbz about 8 years ago
- 4 comments
#144 - describe_Conventions specs are basically empty
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#144 - describe_Conventions specs are basically empty
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#143 - chore(solution): port to .NET Core 1.0
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 4 comments
#143 - chore(solution): port to .NET Core 1.0
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 4 comments
#142 - Update rakefile to .NET Core solution
Issue -
State: open - Opened by BrainCrumbz over 8 years ago
- 4 comments
#141 - build.sh refers to obsolete 2012 solution
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#141 - build.sh refers to obsolete 2012 solution
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#140 - chore(repository): cleanup obsolete projects & files
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 2 comments
#140 - chore(repository): cleanup obsolete projects & files
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 2 comments
#139 - Update nuspec file to current format
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#139 - Update nuspec file to current format
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#138 - Cleanup obsolete projects, build scripts and files
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 4 comments
#138 - Cleanup obsolete projects, build scripts and files
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 4 comments
#137 - chore(repository): delete obsolete, user, local, output files
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
#137 - chore(repository): delete obsolete, user, local, output files
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
#136 - fix(bareCode): avoid NullRef exception after spec c'tor throws
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
#136 - fix(bareCode): avoid NullRef exception after spec c'tor throws
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
#135 - Question: Examples in context are run even if before_all throws an exception
Issue -
State: open - Opened by raghur over 8 years ago
- 7 comments
Labels: rfc
#135 - Question: Examples in context are run even if before_all throws an exception
Issue -
State: open - Opened by raghur over 8 years ago
- 7 comments
Labels: rfc
#134 - NSpec website is broken again: (╯°□°)╯︵ ┻━┻
Issue -
State: closed - Opened by amirrajan over 8 years ago
- 2 comments
#134 - NSpec website is broken again: (╯°□°)╯︵ ┻━┻
Issue -
State: closed - Opened by amirrajan over 8 years ago
- 2 comments
#133 - chore(nspecSpecs): switch from Rhino.Mocks to Moq
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
#133 - chore(nspecSpecs): switch from Rhino.Mocks to Moq
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
#132 - redirect & capture console output and display in context
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 6 comments
#132 - redirect & capture console output and display in context
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 6 comments
#131 - feat(bareCode): avoid blow up with exception in spec class c'tor
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#131 - feat(bareCode): avoid blow up with exception in spec class c'tor
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 1 comment
#130 - xitAsync prints an error message
Issue -
State: closed - Opened by raghur over 8 years ago
- 18 comments
Labels: bug
#130 - xitAsync prints an error message
Issue -
State: closed - Opened by raghur over 8 years ago
- 18 comments
Labels: bug
#129 - .Net Coreify NSpec like all the cool kids
Issue -
State: closed - Opened by amirrajan over 8 years ago
- 17 comments
Labels: enhancement
#129 - .Net Coreify NSpec like all the cool kids
Issue -
State: closed - Opened by amirrajan over 8 years ago
- 17 comments
Labels: enhancement
#128 - describe_output tests failing after elapsed time reported
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 2 comments
#128 - describe_output tests failing after elapsed time reported
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 2 comments
#127 - Ordered specs
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 11 comments
#126 - Report elapsed time for each spec
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 1 comment
#126 - Report elapsed time for each spec
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 1 comment
#125 - feat(context): wrap exceptions from bare code in custom exception
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 12 comments
#125 - feat(context): wrap exceptions from bare code in custom exception
Pull Request -
State: closed - Opened by BrainCrumbz over 8 years ago
- 12 comments
#124 - Update XUnitFormatter to write to file instead of Console
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 3 comments
#124 - Update XUnitFormatter to write to file instead of Console
Pull Request -
State: closed - Opened by raghur over 8 years ago
- 3 comments
#123 - Why exceptions in MethodContext.Build are not caught?
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 13 comments
Labels: enhancement, rfc
#123 - Why exceptions in MethodContext.Build are not caught?
Issue -
State: closed - Opened by BrainCrumbz over 8 years ago
- 13 comments
Labels: enhancement, rfc
#118 - Error when spec and parent both have before_each but one is async and the other isn't
Issue -
State: closed - Opened by tl24 almost 9 years ago
- 16 comments
Labels: bug, rfc
#118 - Error when spec and parent both have before_each but one is async and the other isn't
Issue -
State: closed - Opened by tl24 almost 9 years ago
- 16 comments
Labels: bug, rfc
#114 - Run a single example
Issue -
State: open - Opened by provegard almost 9 years ago
- 20 comments
Labels: enhancement
#114 - Run a single example
Issue -
State: open - Opened by provegard almost 9 years ago
- 20 comments
Labels: enhancement
#108 - Exceptions ignored in before_each or before delegates
Issue -
State: closed - Opened by patroza about 9 years ago
- 11 comments
Labels: bug
#102 - Optional output when executing before/ act/ after hook
Issue -
State: open - Opened by BrainCrumbz about 9 years ago
- 1 comment
Labels: feature
#102 - Optional output when executing before/ act/ after hook
Issue -
State: open - Opened by BrainCrumbz about 9 years ago
- 1 comment
Labels: feature
#91 - NSpec website needs to be redone.
Issue -
State: closed - Opened by amirrajan over 9 years ago
- 12 comments
Labels: enhancement
#91 - NSpec website needs to be redone.
Issue -
State: closed - Opened by amirrajan over 9 years ago
- 12 comments
Labels: enhancement
#79 - Documentation for how the lifecycle of before/each/all/act/it/after should work
Issue -
State: closed - Opened by petemounce almost 10 years ago
- 30 comments
Labels: enhancement
#79 - Documentation for how the lifecycle of before/each/all/act/it/after should work
Issue -
State: closed - Opened by petemounce almost 10 years ago
- 30 comments
Labels: enhancement
#64 - Data-driven tests & dynamically-generated tests
Issue -
State: closed - Opened by petemounce about 11 years ago
- 7 comments
#64 - Data-driven tests & dynamically-generated tests
Issue -
State: closed - Opened by petemounce about 11 years ago
- 7 comments
#61 - AppDomain and CurrentDirectory is different from NUnit.
Issue -
State: closed - Opened by dacat over 11 years ago
- 5 comments
Labels: bug
#61 - AppDomain and CurrentDirectory is different from NUnit.
Issue -
State: closed - Opened by dacat over 11 years ago
- 5 comments
Labels: bug
#59 - expect with assertions
Issue -
State: closed - Opened by sgraf812 over 11 years ago
- 11 comments
#59 - expect with assertions
Issue -
State: closed - Opened by sgraf812 over 11 years ago
- 11 comments
#58 - nspec on xamarin and osx
Issue -
State: closed - Opened by dhf0820 over 11 years ago
- 6 comments
Labels: feature
#58 - nspec on xamarin and osx
Issue -
State: closed - Opened by dhf0820 over 11 years ago
- 6 comments
Labels: feature
#57 - Running Multiple Assembly With Nspec
Issue -
State: closed - Opened by satish860 over 11 years ago
- 5 comments
Labels: feature
#57 - Running Multiple Assembly With Nspec
Issue -
State: closed - Opened by satish860 over 11 years ago
- 5 comments
Labels: feature
#41 - NSpecRunner unable to pull in config file
Issue -
State: closed - Opened by DrSammyD over 12 years ago
- 9 comments
Labels: bug
#41 - NSpecRunner unable to pull in config file
Issue -
State: closed - Opened by DrSammyD over 12 years ago
- 9 comments
Labels: bug
#31 - VS11 Beta - Test Runner Adapter
Issue -
State: closed - Opened by tomsdev almost 13 years ago
- 18 comments