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

Add Java DSL examples in reference guide #196

Closed
Ernesto-Maserati-CH opened this issue Feb 1, 2017 · 4 comments
Closed

Add Java DSL examples in reference guide #196

Ernesto-Maserati-CH opened this issue Feb 1, 2017 · 4 comments

Comments

@Ernesto-Maserati-CH
Copy link

Ernesto-Maserati-CH commented Feb 1, 2017

I would drop support for XML test cases. If someone wants XML they can built a Citrus addon for that.

My guess is that there are very few Citrus users who choos XML test scripts.

When I look into the documentation to me it is "polluted" with XML examples, but I am interested into Java examples.

@christophd
Copy link
Member

I doubt that XML is not wanted in the community. Integration testing is very often done by non-developers such as testers that do not have any Java background. This is what we constantly experience from questions and workshops with customers.

However I see your point that some Java DSL examples are missing in the documentation. This is a result from having XML as first and only way of writing tests in Citrus for years.

@christophd christophd changed the title Test cases in XML Add Java DSL examples in reference guide Feb 1, 2017
@christophd
Copy link
Member

I allowed myself to rename the issue to "adding more Java DSL examples to the reference guide"

@christophd christophd added this to the SOMEDAY milestone Feb 1, 2017
@Ernesto-Maserati-CH
Copy link
Author

Thank you!

Maybe it would be possible to add language bindings to Citrus framework like Selenium has. I am not sure if that would work for Citrus however, I didn't think this through.

As a programmer I never would choose to write the test script in XML format. People who ae not familiar with programming should not lay their hands on test automation in my opinion.

@christophd christophd modified the milestones: v2.7.1, SOMEDAY Feb 9, 2017
@christophd christophd modified the milestones: SOMEDAY, v2.7.1 Mar 9, 2017
@christophd christophd added BACKLOG and removed READY labels Mar 12, 2017
@christophd christophd added READY and removed BACKLOG labels Mar 25, 2017
@christophd christophd added BACKLOG and removed READY labels May 29, 2017
@christophd christophd modified the milestones: SOMEDAY, v2.7.7 May 24, 2018
@christophd christophd modified the milestones: v2.7.7, v2.7.8 Sep 18, 2018
@svettwer svettwer modified the milestones: v2.7.8, v2.8 Oct 12, 2018
@svettwer svettwer removed this from the v2.8 milestone Jan 14, 2019
@svettwer
Copy link
Contributor

svettwer commented Jan 24, 2019

Closed as duplicate of #607 which is on the roadmap for 2019

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

No branches or pull requests

3 participants