Developer onboarding

[gphilipp]

Hi guys,

I'm quite new to Cucumber but I really love it already.
I want to get involved and help get the first version out (I already coded a feature to add support for enums), but I have a few (unrelated) questions :

1. I'd like to add some acceptance tests for my feature but don't know what is the best way to to it ? I saw Aslak added .feature files in the picocontainer module when he added support the java.util.Calendar. But the converters code lives in core... Aren't the features supposed to live there too ?
2. How do you communicate with each other to ask questions related to cucumber-jvm development ? GH issues ? Chat ? Irc ? The cukes google group ?
3. Correct me if i'm wrong but it seems that the master branch currently doesn't pass the tests (because of Xstream not being correctly added as a dependency : test scope used instead of runtime, so that the CLI tests don't run). Did you add the XStream lib directly your IDE (gasp !) ?
4. How do you generate the cucumber (HMTL) reports ? With a maven plugin ? No command line tool like in ruby ?

Sorry for all these questions, but i'm having a hard time to grasp everything. I volunteer to put up a developer_getting_started .md if necessary to lay the foundations :)

Gilles

[aslakhellesoy]

Since you created a ticket, I suppose you want this to be "fixed" by improving the README. Fair enough :-)

FYI: discussions usually happen on the mailing list: https://groups.google.com/forum/?fromgroups#!forum/cukes

[gphilipp]

Thx Aslak, i'll repost my question in the mailing list, and keep this ticket to improve the README for the next newcomer dev..

[aslakhellesoy]

1) Features

The core module is "abstract" - it doesn't have a backend. The java module is "abstract" too (it doesn't have a DI container for instantiating stepdefs), so I tested this in the picocontainer module.

2) Communication

The google group: https://groups.google.com/forum/?fromgroups#!forum/cukes

3) XStream

To prevent version clashes, XStream is a "provoded" dependency in core (see #179). The maven build uses jarjar to package it inside the core module under a new package name.

This means that if you are building/running cucumber-jvm in an IDE using the maven pom to set up the project - other modules won't see XStream classes. Most modules add it back (in optional dependencies) in their poms - see the junit pom for example. If it's missing in a module, just add it in the same way.

4) HTML report

See how it's done in the java-webbit-websockets-selenium examples module

[mlvandijk]

2. Communication
   Also: https://cucumberbdd.slack.com

@plaindocs - Let's include this info in the docs, if still up to date/relevant? So we could close this issue?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

[stale]

This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.