Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
R
relational-rags
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
JastAdd
relational-rags
Commits
0e664d95
Commit
0e664d95
authored
5 years ago
by
Johannes Mey
Browse files
Options
Downloads
Patches
Plain Diff
Update CONTRIBUTING.md
parent
5783e7e8
Branches
Branches containing commit
No related tags found
1 merge request
!8
Resolve "Create guides for contributing"
Pipeline
#5148
passed
5 years ago
Stage: build
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+5
-5
5 additions, 5 deletions
CONTRIBUTING.md
with
5 additions
and
5 deletions
CONTRIBUTING.md
+
5
−
5
View file @
0e664d95
...
...
@@ -8,22 +8,22 @@ Once done (and new tests are written to ensure, a bug is really fixed, and the f
A test usually defines a grammar, optionally some attributes and a Test class.
It then normally runs RelAST followed by JastAdd.
To create a new test, the following four ingredients are
need
ed:
To create a new test, the following four ingredients are
involv
ed:
## Specification
Here, the grammar and attributes to be compiled are contained.
Use
`src/test/jastadd/$YourTestName`
as directory to put your files into.
All generated
`*.ast`
,
`*.j
rag
`
and
`ResolverStubs.jrag`
are already ignored by the main
`.gitignore`
.
All generated
`*.ast`
,
`*.j
add
`
and
`ResolverStubs.jrag`
are already ignored by the main
`.gitignore`
.
## Generated files
## Generated
Java
files
Usually, all files are generated into a separate directory in
`src/test/java-gen/`
.
This location can be
[
configured
](
#build-configuration
)
.
## Build configuration
Currently, test setup is configured within
the
`build.gradle`
using a specialized Gradle task
`RelastTest`
.
Currently,
the
test setup is configured within
`build.gradle`
using a specialized Gradle task
`RelastTest`
.
An example configuration might look like:
```
groovy
...
...
@@ -71,7 +71,7 @@ Furthermore, empty lines, lines starting with `//` and the order of the error me
## Output diff
Currently, there is one test to test whether the output of RelAST is a valid input for RelAST and produces the same output again.
To achieve this, there two Gradle tasks. The first produces the usual
`.ast`
and
`.jadd`
files, whereas the second task takes the
`.ast`
as input.
To achieve this, there
are
two Gradle tasks. The first produces the usual
`.ast`
and
`.jadd`
files, whereas the second task takes the
`.ast`
as input.
The test then ensures, that both output grammars are identical.
# Publishing
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment