-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup1 #113
Open
TPReddy
wants to merge
1,652
commits into
x97mdr:master
Choose a base branch
from
picklesdoc:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
setup1 #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix Issue with Scenario Outline Data Containing Parenthesis
* Update CHANGELOG.md * Version Bump (2.20.0) * Version 2.20.0
* Fix change log * Version 2.20.1
Improve readability of Background by making the .pre class in DHTM styled using a monospaced font
* Initial test * Different tag selection mechanism * More stuff * Fix query and get rid of dynamic * Add combined chart for automated, manual and nottested scenarios * Remove the charts per test kind * Finetuning the chart and renaming a method * Remove unused usings
On a VS test result file containing many tests, the current code is pretty slow. This was observed when migrating a codebase from NUnit3 result files to trx. Here, based on profiling, we improve the performance by caching the parsing of the results: - a lookup of tests per feature - a dictionary of test results per test id On a sample file with about 1000 tests, the performance improves from 40.2 seconds to 2.5 seconds. This was tested with: ``` .\Pickles.exe -f xxx -o xxx --trfmt=vstest --enableComments=false -df=json -lr=xxx.trx ``` The resulting `pickledFeatures.json` file is identical to the one before these changes (except the `GeneratedOn` field). Co-authored-by: Timothée Lecomte <[email protected]>
) * Fix matching of scenario outline with duplicate values with VsTest * Add new scenarios to most other unit test frameworks as well * Update various nuget packages and fix compilation issues * Add the scenario outlines to Cucumber and CucumberJS * Add bindings, test results and tests for Cucumber Ruby * Adding bindings, test results and tests for CucumberJS * Add a sleep because of timing issues Co-authored-by: Dirk Rombauts <[email protected]>
* Corrected mistake and enhanced consistency in the CONTRIBUTING page. * Added new project for Markdown unit tests with initial, inconclusive, test. * Added another new project for Markdown acceptance tests with initial, inconclusive, test. * Initial hook up of Markdown builder and first feature, adding a Title. * Added Markdown document resolver * Refactored, concerns seperated into Stylist and TitleBlock classes. Static text placed in localization resource file for future translations. Some aspects still in builder for later refactoring when the path is clearer. * Updated build scripts to include Markdown library and tests * fix test.fsx error for Markdown.UnitTests reference * Downgrade Specflow to 2.3.2 to attempt build issue fix. Included partial work on Generated Info feature. * Corrected UnitTests namespace, added PicklesDoc. prefix. * Generation Time tested with new TestableDateTime singleton. Ready for refactoring. * Refactor Generation Info, now part of TitleBlock and Localization. * Implemented File Location feature. Scenario: Output is written to specified location * Minor cleanup in Markdown acceptance tests feature and steps * Feature Heading added to Markdown output * Feature Description added to Markdown output * Corrected line spacing for feature description * Feature Tags included in Markdown Output * Scenario Heading added to Markdown document * Added Scenario Tags to Markdown output * Confirm order of content in Markdown output for this acceptance testing * Steps in Scenarios added to Markdown output * Refactor code, documents have lines and different blocks which share a parent class all return collections of lines. * Feature Background included in Markdown Output * New Scenario Outline Feature. Table formatting moved to own class TableBlock ScenarioOutline formatting added in class ScenarioOutlineBlock * Fixed bug #19 - Couldn't write markdown output file Fixed bug #20 - Tags have double @ symbols * Fixed bug #21 - Scenario Outlines missing placeholders - In steps - In Tables * Include Markdown icon files in output folder * Scenario Result included in heading. Stylist updated to process ScenarioHeading TestResult. Updated ScenarioBlock to process TestResult values. Acceptance tests updated to test Scenario Status * Table construction now incudes results when available e.g. in scenario outline examples. * Markdown Stylist updated to include results and code refactored.
* Improve unit tests of CommandLineArgumentParser * Simplify the unit tests of the Markdown format The tests that the generation date is correct make the code much more complicated than necessary. If we want to solve this problem, I prefer a properly injected IDateTimeProvider interface. * Added features to change log
* Version 2.21.0 * The end of the road
* Fix for extra header cell in html output * Version 2.21.1 * Updated to .NET Framework 4.8 * Version 2.3.0 * Version 2.3.0 * Version 2.3.2 * Version 2.3.3
* Add build.yml * move build.yml to workflows
* Update build.yml * Update build.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sdsd