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.

Sign up for GitHub

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

Jump to bottom

Set up some tests with ktest #5

Open
3 of 6 tasks
ayberkt opened this issue Jun 2, 2017 · 1 comment
Open
3 of 6 tasks

Set up some tests with ktest #5

ayberkt opened this issue Jun 2, 2017 · 1 comment

Comments

@ayberkt
Copy link
Collaborator

ayberkt commented Jun 2, 2017 •
edited
Loading

At this point we can start testing our K operational semantics by adding some hand-written GHC Core programs.

To use ktest for testing, we should specify the designated output in the x.out file in test/pkore-samples for the following hand-written GHC Core programs.

  • Case-2.pkore
  • Case.pkore
  • Identity.pkore
  • Lambda.pkore
  • Let-1.pkore
  • Let-2.pkore
ayberkt added a commit that referenced this issue Jun 2, 2017
@ayberkt
ktest .out files for Identity.pkore and Lambda.pkore (for #5)
1726e2c
ayberkt added a commit that referenced this issue Jun 2, 2017
@ayberkt
config.xml for ktest (for #5)
1a1e79c
@ayberkt
Copy link
Collaborator Author

ayberkt commented Jun 2, 2017

@bmmoore can you verify some time that the output files Identity.pkore.out and Lambda.pkore.out are indeed what should be expected? We looked at them with @lucaspena yesterday and decided that they look fine, but it would be nice if you take a look as well.

ayberkt added a commit that referenced this issue Jun 2, 2017
@ayberkt
Add Let-2.pkore.out (for #5)
0f48c4b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ayberkt