Comments (16)
I plan to contribute support for JUnit Plug-in and SWTBot tests.
Is there recommendation for the Xtext version which should be used?
from lcdsl.
https://mduft.github.io/lcdsl-latest has been updated with the 0.3.0 version which includes #36 - Thanks @glatuske for the contribution!
from lcdsl.
This is still an open point. Unit tests are right now not supported. All dependencies are there, it's just a TODO... contributions of course more than welcome :)
from lcdsl.
Yay, great! :) I currently use Xtext 2.19.0, but I assume it would work with slightly different versions without any change. If you need smallish guidance through the code, feel free to contact me anytime :)
from lcdsl.
I used 2.19 too. That results in small changes in almost every generated file.
Is there a general minimal required Eclipse version? Probably this would restrict the Xtext version.
The major implementation part is already done. I'm still want to update the documentation and fix some issues on auto completion. Because I did the implementation as part of a hackathon at my company, I need an approval for the contribution. So I hope, I can provide you the first version for review before Christmas.
from lcdsl.
This is great to hear! Are you on Windows? Maybe line endings (I'm on Linux)? Or is it actual code changes? Whatever it is, as long as the generated code works we're fine here IMHO :) Eagerly awaiting the pull request!
from lcdsl.
I'm working on Windows. I'll check the line endings. But I think it's more about the comment in each Java file:
/*
- generated by Xtext 2.19.0
*/
from lcdsl.
OK. As long as you're based of off the current master, I'm OK with all the files changing :)
from lcdsl.
Hello Markus!
In your LcDsl presentation on the EclipseCon Europe 2018 (at 17:50 minute) you mentioned that it is possible with LcDsl to specify environment variables to run automated ui tests on different display. I would like to run the Xtext Domainmodel example (File -> New -> Example... -> Xtext Examples -> Xtext Domain-Model Example) Plug-in Tests (org.eclipse.xtext.example.domainmodel.ui.tests
) on the secondary display.
Could you please help me how to define such a launch configuration in LcDsl?
Thank you very much for your help in advance!
Tamás
from lcdsl.
Hi. You're right, I said that :) but we were (are) not using Plug-in Test Launch Configurations. Our tests run as "normal" eclipse launch configuration. LcDsl still has no support for Unit Test Launch Configurations at all right now - it needs to be added...
from lcdsl.
Do you know how to configure that using the standard Eclipse Launch Configuration mechanism? Once I make it work using the standard way (without LcDsl) , I can add this support to LcDsl as well.
from lcdsl.
Unfortunately we're not using actual 'tests' at all - we're using a plain Eclipse application to run our custom test framework, so no, sorry :|
from lcdsl.
Maybe you can help me how it is possible to make a plain Eclipse application run on a secondary display?
from lcdsl.
Sure, on linux you need to set DISPLAY in the launch configuration like this:
environment DISPLAY=":5";
Then start a Xephyr or Xvfb on :5 before launching - this should do the trick...
from lcdsl.
Thanks, I will give it a try!
from lcdsl.
Fixed by #36
from lcdsl.
Related Issues (20)
- new feature: Link to products / features / plugins HOT 3
- Provide default ID for launch config
- new feature: Add required dependencies HOT 3
- Working Sets HOT 1
- Easy access to raw launch configuration file HOT 1
- Missing ignored plugins should not generate a warning
- Updating the Xtext Community Website HOT 3
- NPE with unknown launch types HOT 5
- Missing latest version of org.eclipse.debug.ui.launchview HOT 2
- Startlevels for workspacebundles HOT 6
- Test class not accepting all JUnit5 variants HOT 1
- Support launch type pure JUnit? HOT 1
- Application `[No Application] - Headless Mode` unsupported. - Should be default HOT 1
- regression: CI build hangs at "loading target platform" HOT 3
- Validation for test class is too strict
- Compile error due to using API 11, but 1.8 on classpath HOT 1
- Introduction of variables in lcdsl
- Test container plugin dependencies should be added automatically
- Plugins attribute should not be required if test container points to a plugin project
- Typing `${folder_prompt}` in `working-dir` crashes the IDE
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lcdsl.