csf-dev/CSF.Screenplay

Issues

• To integrate with current versions, screenplay must support the latest SpecFlow

  #186 opened 4 years ago by craigfowler
  0

• To learn how to use Screenplay with SpecFlow, devs must be able to read a tutorial

  #155 opened 6 years ago by craigfowler
  5

• To read docs, the wiki page about the Report Conversion Utility must be written

  #173 opened 5 years ago by craigfowler
  3

• NUnit tutorial code does not compile

  #185 opened 5 years ago by kevinpohlmeier
  1

• To learn how to use Screenplay with NUnit, devs should be able to read a tutorial

  #154 opened 6 years ago by craigfowler
  0

• To read docs, the page about NuGet packages must be written

  #171 opened 5 years ago by craigfowler
  0

• AppVeyor CI is failing builds due to an issue with the Web API project

  #183 opened 5 years ago by craigfowler
  0

• Consider merging the Screenplay.Reporting package into the main Screenplay one

  #184 opened 5 years ago by craigfowler
  0

• JSON to HTML conversion NuGet package has excess dependencies

  #182 opened 5 years ago by craigfowler
  0

• To link the MIT license properly, use the correct NuGet element

  #181 opened 5 years ago by craigfowler
  0

• Dependencies on Newtonsoft JSON should be relaxed

  #180 opened 5 years ago by craigfowler
  0

• A packaging error means that the HTML report converter cannot be executed

  #179 opened 5 years ago by craigfowler
  0

• To better compress CSS & JavaScript in generated reports, webpack should be used in the build process

  #178 opened 5 years ago by craigfowler
  0

• To reduce the weight of JavaScript on the page, the HTML reports should not use jQuery

  #177 opened 5 years ago by craigfowler
  0

• To direct readers to docs, the README should link to the wiki

  #176 opened 5 years ago by craigfowler
  0

• To keep it up to date, the sample test in the README must be updated

  #175 opened 5 years ago by craigfowler
  0

• To simplify and remove redundant boilerplate, the configuration of reports should be revisited

  #159 opened 5 years ago by craigfowler
  2

• To simplify it, remove unneeded methods from the ICast API

  #158 opened 5 years ago by craigfowler
  0

• To assist devs, create some developer guidelines

  #174 opened 5 years ago by craigfowler
  1

• To learn about Tasks, devs should be able to read a wiki page about them

  #153 opened 5 years ago by craigfowler
  1

• To read docs, the wiki page about Object Formatters must be written

  #172 opened 5 years ago by craigfowler
  0

• To read docs, the page about writing new integrations must be written

  #170 opened 5 years ago by craigfowler
  0

• To read docs, the Extensibility wiki page must be written

  #169 opened 5 years ago by craigfowler
  0

• To read docs, the Screenplay Reference hub must be written

  #168 opened 5 years ago by craigfowler
  0

• To read docs, the wiki page about writing tests must be written

  #167 opened 5 years ago by craigfowler
  0

• To read docs, the wiki page about the Stopwatch must be written

  #166 opened 5 years ago by craigfowler
  0

• To read docs, the JSON API wiki page must be written

  #165 opened 5 years ago by craigfowler
  0

• To read docs, the wiki page for writing tasks must be written

  #164 opened 5 years ago by craigfowler
  0

• To read docs, the wiki page about getting actors must be written

  #163 opened 5 years ago by craigfowler
  0

• To read docs, reference about the Integration Configuration must be written

  #162 opened 5 years ago by craigfowler
  0

• To read installation docs, the wiki page for SpecFlow must be written

  #161 opened 5 years ago by craigfowler
  0

• To read installation docs, the wiki page for NUnit must be written

  #160 opened 5 years ago by craigfowler
  0

• Wiki pages are improperly linked because the links include file extensions

  #152 opened 5 years ago by craigfowler
  1

• The documentation wiki must link articles properly

  #157 opened 5 years ago by craigfowler
  1

• A packaging error means that the JSON to HTML converter cannot be installed

  #156 opened 5 years ago by craigfowler
  0

• To illustrate the architecture of a Screenplay test, devs should be able to read a diagram from the wiki

  #151 opened 5 years ago by craigfowler
  1

• To illustrate Screenplay's place within a testing solution, devs should be able to read a diagram in the wiki

  #150 opened 5 years ago by craigfowler
  1

• In order to make serialization and manipulation easier, the Report model must be refactored into POCOs

  #148 opened 6 years ago by craigfowler
  1

• To get HTML reports, devs should have a CLI app to create them from JSON

  #145 opened 6 years ago by craigfowler
  1

• Cannot write HTML reports: Crash error (strongly-named assemblies)

  #141 opened 6 years ago by craigfowler
  5

• AppVeyor build is failing due to an HTTP 500 error in web API tests

  #149 opened 6 years ago by craigfowler
  0

• Create a reporter which immediately writes to a JSON stream

  #147 opened 6 years ago by craigfowler
  2

• Suppress 'meaningless' Feature/Scenario IDs in HTML reports

  #144 opened 6 years ago by craigfowler
  1

• Every line in an HTML report must be foldable

  #146 opened 6 years ago by craigfowler
  0

• Suppress Given/When/Then when showing "gain ability" items in HTML reports

  #142 opened 6 years ago by craigfowler
  1

• Prevent exception stack traces from being duplicated in HTML reports

  #143 opened 6 years ago by craigfowler
  0

• Strongly name all Screenplay assemblies

  #139 opened 6 years ago by craigfowler
  0

• Add additional overloads to the Stage implementation, supporting limited Cast-related functionality

  #138 opened 6 years ago by craigfowler
  0

• Remove C# expressions in report document

  #140 opened 6 years ago by craigfowler
  0

• Performance: Writing HTML reports is incredibly slow

  #137 opened 6 years ago by craigfowler
  2