mslisamarieOccasional ContributorJoined 4 years ago13 Posts3 LikesLikes received3 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsRe: PickleEvent not working Cucumber uplift 7.0.0 You should use PickleWrapper and Pickle and String Tag instead since PickleEvent and PickleTag now is deprecated. Here is a small example: for (final String tagg : wrapper.getPickle().getTags()) { if (tag.equals(tagg)) { foundPickles.add(wrapper.getPickle()); Best Regards Lisa Marie Re: Error when running DataTables in Cucumber 7.0.0 The problem has been solved. If someone stumbles upon the same issue as me the asMaps should be changed to asEntries. Re: How to execute all scenarios in same browser session using Cucumber 6.10.0 version? Is it Possible ? You are very welcome! I am unsure if you RameshKorla needed code examples but if so there are many tutorials online on how to create feature files and turn them into code. Here is one link for example: Cucumber Scenario Outline Example - JavaPointers Best Regards Lisa Marie Error when running DataTables in Cucumber 7.0.0 Hello! I have stumbled upon many issues regarding my Cucumber Uplift to version 7.0.0 and I cannot seem to find a solution for this error: Can't convert DataTable to List<Map<class java.lang.String,class java.lang.String>>. You have to write the conversion for it in this method. I cannot add the code here since its confidential but do you know how to solve this issue? The method uses DataTableWrapper and from what I have read the issue should be solved by changing getMaps to getLists but that does not work for me. All kinds of help would be greatly appreciated! Best Regards Lisa Marie SolvedRe: How to execute all scenarios in same browser session using Cucumber 6.10.0 version? Is it Possible ? Each scenario reruns the driver creation code which creates a new instance of your browser. In your Feature file you can write all scenarios you want to run. You can read more here: Top New Features of Cucumber JVM v6 - Automated Visual Testing | Applitools How can I make the annotation @ParemeterType use a list? Hello! As I am continuing my Cucumber 7.0.0 uplift journey I have stumbled upon some issues. The old way on how to handle parameter types is deprecated so now the annotations @ParameterType and @DataTableType are used instead. My problem is that we are using many enums (I cannot show you how the real code looks like since I signed an NDA) and before they were looped through in an Array stream. To make it work now I have to hardcode the enums in the value field like this: @ParameterType(name = "animal_type", value "(CAT|HORSE|DOG|DONKEY|PIG)") public Animal defineAnimalType(final String animalType) { return Animal.fromString(animalType); } And this is not an optimal solution because if the enums needs to be changed in the future people need to look up the hardcoded strings and change there as well. I read about something called @DefaultParameterTransformer and I wonder if that can be an option. Does anyone have a suggestion or solution for this problem? I would really appreciate it! Best Regards Lisa Marie Re: Strict removed from CucumberOptions I thought strict was the issue all along but the issue was with the class TypeRegistryConfiguration which no longer implemented TypeConfigurer since its deprecated. So all methods needed to be re-written using the annotation @ParameterType. Stated in this example here: [Core] Deprecate TypeRegistryConfigurer (#1799) · cucumber/cucumber-jvm@bd4cd22 · GitHub otherwise the run will crash. Re: Strict removed from CucumberOptions It works now I found a nice workaround. Thanks! Strict removed from CucumberOptions Hello everyone! In Cucumber 7.0.0 the strict in @CucumberOptions is deprecated. So when running a test case I get the error: Unable to parse scenario probably due to unimplemented features. Which clearly shows that I cannot run a test case unless strict is a part of the CucumberOptions. Has anyone stumbled upon this issue and knows a solution for it? Best Regards Lisa Marie SolvedRe: PickleEvent not working Cucumber uplift 7.0.0 The issue has been resolved so this ticket can be closed.