issues
search
csf-dev
/
CSF.Screenplay
Implementation of the Screenplay pattern (aka Journey) in .NET
https://csf-dev.github.io/CSF.Screenplay/
MIT License
13
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
AppVeyor CI is failing builds due to an issue with the Web API project
#183
craigfowler
closed
5 years ago
0
JSON to HTML conversion NuGet package has excess dependencies
#182
craigfowler
closed
5 years ago
0
To link the MIT license properly, use the correct NuGet element
#181
craigfowler
closed
5 years ago
0
Dependencies on Newtonsoft JSON should be relaxed
#180
craigfowler
closed
5 years ago
0
A packaging error means that the HTML report converter cannot be executed
#179
craigfowler
closed
5 years ago
0
To better compress CSS & JavaScript in generated reports, webpack should be used in the build process
#178
craigfowler
closed
4 weeks ago
2
To reduce the weight of JavaScript on the page, the HTML reports should not use jQuery
#177
craigfowler
closed
4 weeks ago
1
To direct readers to docs, the README should link to the wiki
#176
craigfowler
closed
5 years ago
0
To keep it up to date, the sample test in the README must be updated
#175
craigfowler
closed
5 years ago
0
To assist devs, create some developer guidelines
#174
craigfowler
opened
5 years ago
1
To read docs, the wiki page about the Report Conversion Utility must be written
#173
craigfowler
opened
5 years ago
3
To read docs, the wiki page about Object Formatters must be written
#172
craigfowler
closed
1 month ago
0
To read docs, the page about NuGet packages must be written
#171
craigfowler
closed
5 years ago
0
To read docs, the page about writing new integrations must be written
#170
craigfowler
closed
1 month ago
0
To read docs, the Extensibility wiki page must be written
#169
craigfowler
closed
1 month ago
0
To read docs, the Screenplay Reference hub must be written
#168
craigfowler
closed
2 months ago
1
To read docs, the wiki page about writing tests must be written
#167
craigfowler
closed
1 month ago
0
To read docs, the wiki page about the Stopwatch must be written
#166
craigfowler
closed
1 month ago
1
To read docs, the JSON API wiki page must be written
#165
craigfowler
closed
1 month ago
1
To read docs, the wiki page for writing tasks must be written
#164
craigfowler
closed
2 months ago
1
To read docs, the wiki page about getting actors must be written
#163
craigfowler
closed
2 months ago
1
To read docs, reference about the Integration Configuration must be written
#162
craigfowler
closed
1 month ago
1
To read installation docs, the wiki page for SpecFlow must be written
#161
craigfowler
closed
1 month ago
1
To read installation docs, the wiki page for NUnit must be written
#160
craigfowler
closed
2 months ago
1
To simplify and remove redundant boilerplate, the configuration of reports should be revisited
#159
craigfowler
closed
5 years ago
2
To simplify it, remove unneeded methods from the ICast API
#158
craigfowler
closed
5 years ago
0
The documentation wiki must link articles properly
#157
craigfowler
closed
5 years ago
1
A packaging error means that the JSON to HTML converter cannot be installed
#156
craigfowler
closed
5 years ago
0
To learn how to use Screenplay with SpecFlow, devs must be able to read a tutorial
#155
craigfowler
closed
1 month ago
5
To learn how to use Screenplay with NUnit, devs should be able to read a tutorial
#154
craigfowler
closed
1 month ago
1
To learn about Tasks, devs should be able to read a wiki page about them
#153
craigfowler
closed
5 years ago
1
Wiki pages are improperly linked because the links include file extensions
#152
craigfowler
closed
5 years ago
1
To illustrate the architecture of a Screenplay test, devs should be able to read a diagram from the wiki
#151
craigfowler
closed
5 years ago
1
To illustrate Screenplay's place within a testing solution, devs should be able to read a diagram in the wiki
#150
craigfowler
closed
5 years ago
1
AppVeyor build is failing due to an HTTP 500 error in web API tests
#149
craigfowler
closed
6 years ago
0
In order to make serialization and manipulation easier, the Report model must be refactored into POCOs
#148
craigfowler
closed
6 years ago
1
Create a reporter which immediately writes to a JSON stream
#147
craigfowler
closed
6 years ago
2
Every line in an HTML report must be foldable
#146
craigfowler
closed
6 years ago
0
To get HTML reports, devs should have a CLI app to create them from JSON
#145
craigfowler
closed
6 years ago
1
Suppress 'meaningless' Feature/Scenario IDs in HTML reports
#144
craigfowler
closed
6 years ago
1
Prevent exception stack traces from being duplicated in HTML reports
#143
craigfowler
closed
6 years ago
0
Suppress Given/When/Then when showing "gain ability" items in HTML reports
#142
craigfowler
closed
6 years ago
1
Cannot write HTML reports: Crash error (strongly-named assemblies)
#141
craigfowler
closed
6 years ago
5
Remove C# expressions in report document
#140
craigfowler
closed
6 years ago
0
Strongly name all Screenplay assemblies
#139
craigfowler
closed
6 years ago
0
Add additional overloads to the Stage implementation, supporting limited Cast-related functionality
#138
craigfowler
closed
6 years ago
0
Performance: Writing HTML reports is incredibly slow
#137
craigfowler
closed
6 years ago
2
To improve readability, the styling of HTML reports should be improved
#136
craigfowler
closed
5 years ago
1
Consider allowing the cast to resolve services
#135
craigfowler
closed
6 years ago
0
Build the concept of Personas directly into the Cast
#134
craigfowler
closed
6 years ago
0
Previous
Next