Eclipse Community Forums: TMF (Xtext) » correct reference problem with import statement and unti-test

Home » Modeling » TMF (Xtext) » correct reference problem with import statement and unti-test(No reference between import-statement and calling other files. No reference bewtween files at unit-testing.)

Show: Today's Messages :: Show Polls :: Message Navigator

correct reference problem with import statement and unti-test [message #1241881]

Sat, 08 February 2014 17:52

Marcel Lgs

Messages: 9
Registered: February 2014

Junior Member

Hello,

I want to create a dsl with xtext. The new dsl should describe the sequence of tests. With an xml-generator i convert the new dsl to a xml file that a programm can read.
I have a problem with the import-statement and the references. I search two days at the internet, but found no solution for my problem.

Here is my project (simplified):

The Target:
please look into the file at-files.txt (i cannot load the code here)

Explanation:
run and call are key words. With run you can run a test and with call you can call a other test (full test (call AT01) or a test step (call AT01.method1)).

The problem:
When I have the folowing project structure:
/root/files1/AT02.atd
/root/files1/AT01.atd
/root/files2/AT01.atd
The reference in the file AT02.atd are not always correct. Sometimes there are the reference to /root/files2/AT01.atd or sometimes to /root/files1/AT01.atd. There are no check if the import file existes or a reference between the import-statement at the top of the file and the call statement.
I want the exact reference to the file AT01.atd with the import-statment. A nive-to-have is an autocomplete for the import-statement. But I do not know how to Sad

.

The implementation:

The Grammar:
please look into the file grammar.xtext (i cannot load the code here)

The workflow (snippet):
I have these lines at the workflow for the import problem

// scoping and exporting API
fragment = scoping.ImportNamespacesScopingFragment auto-inject {}
fragment = exporting.QualifiedNamesFragment auto-inject {}
fragment = builder.BuilderIntegrationFragment auto-inject {}

Unit-testing with import-references:
My second problem is the import-references at the unit-testing.
introduction: I want to test the xml-generator. So I create in the package *.tests a file GeneratorTest.xtend. In a other package *.files I have the files AT01.atd and AT02.atd (from above) and the correct xml-files (self-written) to these atd-files.
My Attempt: I read in the GeneratorTest.xtend the files AT01.atd and AT02.atd. Then I call the generator and I have in the package *.files.gen the new xml-files). Then I want to compare the self-written xml-files and the generated xml-files.
The Problem: There are no references between the files.

please look into the file unitTest.xtend (i cannot load the code here)

The Problem: the res is null.
How can I test correct my xml-generator (compare self written xml file with generated xml file).

Attachment: grammar.xtext
(Size: 0.57KB, Downloaded 95 times)
Attachment: at-files.txt
(Size: 0.25KB, Downloaded 185 times)
Attachment: unitTest.xtend
(Size: 0.92KB, Downloaded 107 times)

Breadcrumbs

Sign up to our Newsletter