Skip to content
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

Search for multiple tags in DHTML version #283

Closed
dirkrombauts opened this issue Feb 11, 2016 · 10 comments
Closed

Search for multiple tags in DHTML version #283

dirkrombauts opened this issue Feb 11, 2016 · 10 comments

Comments

@dirkrombauts
Copy link
Member

Currently the DHTML version allows to search for only one tag at a time. In larger specifications, there are often many tags used in specific combinations. It would be beneficial if we could search for multiple tags.

@dirkrombauts
Copy link
Member Author

@albertdabrowski could you please enhance this description? One of the questions I have is:

Given I have these scenarios:

@tag1
Scenario: Scenario 1

@tag1 @tag2
Scenario: Scenario 2

@tag 2
Scenario: Scenario 3

When I search for "@tag1 @tag2"
Then the result is ???

@albertdabrowski
Copy link

In our case we would like to have "OR", but I think "AND" would be also valuable. So I think in this case it's a matter of search capability. Do we want to keep it simple or more like for example search in JIRA?

@dirkrombauts
Copy link
Member Author

OR would mean that

When I search for "@tag1 @tag2"
Then the result is "Scenario 1, Scenario 2, Scenario 3"

Right? I'm happy you said OR, because the OR behaviour is consistent with many other search-by-property search definitions that treat different properties as AND criteria, and different values of the same property as OR criteria.

I have to admit I have no experience with JIRA.

@dirkrombauts
Copy link
Member Author

@aaronjrich would you have a moment to get in touch with me? I'd like to ask you a few questions about the DHTML version, with the goal that I am able to extend it myself. I feel bad about having to bother you every time something with the DHTML version comes up.

@aaronjrich
Copy link

@dirkrombauts, sorry about not getting back sooner. Let me know what time works for you.

@dirkrombauts
Copy link
Member Author

@aaronjrich tomorrow (19 February) in the forenoon would work for me (for example). I'm in GMT+2, I don't know which timezone you are in ...

BTW, if you are on gitter, you can send me a message there, that's perhaps easier than filling up this feature request.

@aaronjrich
Copy link

Apparently gitter is blocked here where I work. Is there another way to proceed with this?

@dirkrombauts
Copy link
Member Author

You can email me at dirk dot rombauts at picklesdoc dot com . Does Skype work at your workplace?

dirkrombauts added a commit that referenced this issue Apr 12, 2016
* Fix failing tests by removing overspecification

* Untabify

* Ensure description of feature is never null, fixes crashes of word and excel generation

* Unit test

* SpecFlow conformant name mapping 

* Implement name mapping in nunit signature builder more conformant to SpecFlows name generation logic wrt. to special characters

* Unit tests for special character handling

* Basic comments handling (#311)

* basic comment handling

* add excel handling

* cleanup

* clean up

* fix tests

* handle comments after the last step of a scenario

* clean up

* codestyle clean up

* codestyle clean up

* add test for mapper on comments

* clean up

* adding mapper tests on comments and location
+ more clean up

* Update Nuget packages (and small fixes) (#310)

* Update-Package SpecFlow

* Update-Package Nunit

* ExpectedException is obsolete in nunit3

* Update-Package System.IO.Abstractions.*

* Refactor CurrentScenarioContext to be instance-based and to be injected

* Update-Package MahApps.Metro

* Update-Package AutoMapper

* Update-Package Newtonsoft.Json

* Remove IKVM assembly binding redirects

* Do not use ScenarioContext.Current

* tweak gitignore

* Update GhostDoc file

* Downgrade Automapper to last known good version

* Exclude test project from test coverage

* Edit applicationhost.config

* Added support for multiple tags when searching (issue #283) (#319)

* Use Gherkin 4 parser (#322)

* Update-Package Gherkin

* tweak applicationhost.config

* Factory creates a GherkinDocument now

* The parser now returns a GherkinDocument

* Map a GherkinDocument to a Feature

* Use new icon (#323)

* Use new icon

* Use a big png file with the new logo

* Use the new .png file in the .nuspec files

* Use visual studio 2015

* Version bump to 2.6.0

* Update change log
@dirkrombauts
Copy link
Member Author

Released in version 2.6.0

@albertdabrowski
Copy link

Great, thanks for the efforts.

Appreciate,
Albert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants