Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Eric Kessler
    @enkessler

    Just a reminder, this a room more about Gherkin and the usage thereof, rather than any particular flavor of Cucumber. There are specific rooms for Cucumber implementations: https://gitter.im/cucumber/cucumber-js

    I would be surprised if any implementation did preprocessing of a feature file in that kind of manner. That being said, YOU could certainly do some preprocessing and perhaps have a template file from which you could generate separate feature files for the different sets of data.

    wynnfarm
    @wynnfarm
    @enkessler thanks, I'll check cucumber out.
    Rafael Prates
    @rafaelsprates_twitter
    Hello people. I was used to Automate with JS, but now I got a Java project and I'm in doubt with two things:
    from JS ( not) to Java.
    From JS (click|doubleClick) to Java.
    leemuar
    @leemuar
    Hey, folks!
    gherkin-languages.json has a * symbol in some places:
    ```
      "ru": {
        "and": [
          "* ",
          "И ",
          "К тому же ",
          "Также "
        ],
        "background": [
          "Предыстория",
          "Контекст"
        ],
        "but": [
          "* ",
          "Но ",
          "А "
    ],
    what does it mean? Im writing a custom multilang gherkin parser and Im stuck on this "*", don't know how to interpret it
    Eric Kessler
    @enkessler

    @leemuar It is the "I'm not bothering with a keyword because it doesn't matter in this context" symbol.

    Aside from that, I am curious why you are writing your own parser instead of using one of the many official ones?

    leemuar
    @leemuar
    @enkessler Thanks! Im writing a parser for a rare language that has no official Gherkin parser
    Eric Kessler
    @enkessler
    Rare language, eh. What's hip these days?
    leemuar
    @leemuar
    @enkessler 1C:Enterprise, a platform for automating a company’s financial and wider operational activities, popular in CIS countries. It has it's own programming language, much like VBA
    Eric Kessler
    @enkessler
    I usually only hear about VBA Script in horror stories.
    I think that there are instructions for making parsers for new languages. If not, it is, in theory, straightforward. I've never tried it myself, though.
    Gáspár Nagy
    @gasparnagy
    @leemuar especially for a vba-like language it should be pretty straitforward, you can use the Ruby and the .NET as examples.
    let me know if you get stuck
    leemuar
    @leemuar
    @enkessler @gasparnagy Thanks!
    Fla
    @Flaburgan
    Hi everyone. The documentation at https://cucumber.io/docs/reference#step-definitions only indicates "TODO" about how to parse Data Table Argument. Where can I find example in Java?
    Marit van Dijk
    @mlvandijk
    @Flaburgan Here's an example: http://www.thinkcode.se/blog/2014/06/30/cucumber-data-tables - and Thomas has several other examples also on his blog I think. Or try this github example: https://github.com/tsundberg/cucumber-datatables
    Simon Paitrault
    @Freyskeyd
    Hello, I must start a complete QA testing over a large application. I would like to use gherkin to write specification. But I can't decide which tool, I don't have any language in mind. I just want to do BDD, visual regression, etc
    I know it's a hard question but I'm a little lost
    I tried Behat, it was cool but what's about others options?
    what's about selenium?
    Marit van Dijk
    @mlvandijk
    Hi Simon, it's hard to advice not knowing more about the context. Are you working with the developers or testing an application built by another team/company? If the same team/company, will you be collaborating with them? ) in which case I'd advice using the same language as the project, and storing your test code in the same project). Do you "have to" automate through the UI? (This might be the case if application is build by external vendor) In that case, you'll most likely end up using Selenium (although I've hearing good things about cypress.io which works differently but is only available in JavaScript). If you don't have to go through the UI but can test at "lower" level like REST endpoints, I'd recommend that over Selenium/UI tests as much as possible, as it's faster/easier/less brittle. As far as BDD; will the application actually be built using BDD, or what is the reason you'd want to use Gherkin/BDD? Hope this helps :)
    Simon Paitrault
    @Freyskeyd
    Thank's @mlvandijk for this helpful answer. I'm working with the developers. It's our product. We have a microservices architecture, with many languages (php, node, scala, go, rust). I want to automate the UI testing and also the API testing. I would like to use Gherkin to be able to write feature/story and test it against the product.
    Marit van Dijk
    @mlvandijk
    Does the UI testing actually test the UI, or does it use the UI to test the business process. In which case, you might consider moving most of those tests to the API layer. and only test whatever (hopefully little) logic there is in the FE through the FE.
    That's at least what my team tries to do. Even though we do have a few tests running through the UI on the test environment. That's mainly a smoke test, since we also rely on services made by other teams (and I'd like to at least see it work on an actual environment before deploying to production). Most if not all of "our" business logic is tested before then (& by stubbing external dependencies)
    One thing I've noticed happen is that existing manual regression tests are automated as it. While with automation you can do so much more...
    Simon Paitrault
    @Freyskeyd
    hello @mlvandijk The UI tests are run to validate UX and UI. Also CSS regression.
    Dono Greeff
    @Greeff
    Hello, I agree with Marit here that you would want your BDD tests to test the business flows, so keeping it API based. @Freyskeyd For the UI/UX testing have you considered something like MABL?
    Simon Paitrault
    @Freyskeyd
    @Greeff I can't test API directly because a lot of features are dependent of the presence of the UI
    What do you mean by API based (maybe I don't understand)
    Simon Paitrault
    @Freyskeyd
    @Greeff MABL looks good but I don't have a lot of budget for that. I need to prove the viability of such tests first.
    Dono Greeff
    @Greeff
    Apologies, I made the assumption that your UI's would have been built on the API's given the microservice architecture. UI tests using a BDD tool like cucumber is often expensive as it takes a long time to execute. Also if the UI is changing quite often there is the re-work cost for every change in you automation. These costs can be put together to build a business case for using a tool that handles UI automation in a better fashion. Currently I believe MABL is free for public BETA. No harm in trying it out and then offering it as a showcase for consideration.
    Regarding the API based vs UI based... It is good practice to keep the user journey tests away from GUI test automation as they should be separate scopes. Also generically UI automation only tests on code assertions, not whether the UI looks good from a UX perspective.
    Simon Paitrault
    @Freyskeyd
    Ok, in fact I need to make test like this one:
    • Connect one user to a particular page (on the app), press one button or two. add a text in a box
    • Connect another user and interact with the first one and validate that both can communicate and everything is ok.
    And I also want my PO/PM to write acceptance tests which will run automaticly. Also regression tests (visual/etc)
    Dono Greeff
    @Greeff
    Cucumber is generally used from a (singular) users view. However if written creatively can still work fine considering 2 users. I personally have broken that better practice to good effect. It really comes down to what works best for you.
    Regarding the PO/PM writing the acceptance tests, Just make sure they understand having D R Y gherkin.
    Who will code the automated part of this test suite? You will need to consider that too.
    Simon Paitrault
    @Freyskeyd
    PM already know how to write gherkin, developers will do the code in background
    Dono Greeff
    @Greeff
    Knowing how to write gherkin and keeping it D.R.Y are two different things ;) It will also help to lesson the load onto the developers as they wont have to duplicate work on existing steps etc.
    Simon Paitrault
    @Freyskeyd
    yep
    I'm really confused about what I must do
    I want to test the end user application to replicate common usage before and after deployment. I don't want to touch the architecture (system, DB)
    I was thinking of writting gherkin tests (representing what we manualy do for now)
    but I want something helpful and easy to understand
    Dono Greeff
    @Greeff
    As in a guide to follow in how to start from scratch?
    Simon Paitrault
    @Freyskeyd
    yes
    start small to validate and then improve to something that really work and make my product stronger and my team more confident on deplyoment
    Dono Greeff
    @Greeff
    Yes that is a good approach to take.