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

Command line debugging tests fail when compiling multiple umple files for one test #1175

Open
JoshuaMcManus opened this Issue Dec 5, 2017 · 3 comments

Comments

Projects
2 participants
@JoshuaMcManus

JoshuaMcManus commented Dec 5, 2017

Brief Description

Refer to Issue #882 to see changes made for command line debugging. (See all ignored tests in testbed/test/cruise.compiler.CompilerErrorOutputTests)

The command line debugging tool seems to be functioning correctly for the issues these tests test for, but for some reason the tests themselves fail to execute correctly. When Umple compiles multiple files in order to generate one or more Java files, it claims that it cannot find a symbol from a file that is used by the main file being compiled.

Minimum Steps to Reproduce

There are already 3 tests created in cruise.compiler.CompilerErrorOutputTests, simply removing the @ ignore annotation and running the JUnit test will show you the error

  1. Navigate to the following file: testbed/cruise.compiler.CompilerErrorOutputTests
  2. Find "MultipleClassesTest" and remove the @ ignore annotation above it
  3. Run the JUnit test for the file and observe the failure message

Expected Result

You can view the expected results for the three tests in testbed/test/cruise.compiler.expected

@TimLethbridge

This comment has been minimized.

Show comment
Hide comment
@TimLethbridge

TimLethbridge Dec 5, 2017

Member

I am raising the priority on this, since this is an important problem.

Member

TimLethbridge commented Dec 5, 2017

I am raising the priority on this, since this is an important problem.

@TimLethbridge

This comment has been minimized.

Show comment
Hide comment
@TimLethbridge

TimLethbridge Feb 14, 2018

Member

In particular, the build of Umple itself, which operates on multiple files has this problem

Member

TimLethbridge commented Feb 14, 2018

In particular, the build of Umple itself, which operates on multiple files has this problem

@TimLethbridge

This comment has been minimized.

Show comment
Hide comment
@TimLethbridge

TimLethbridge Jun 23, 2018

Member

See also #1173

Member

TimLethbridge commented Jun 23, 2018

See also #1173

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