Update testPoissonAccuracy.m

[Tony-Drummond]

I removed 8th order test

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Example
• Documentation

Description

Current test implementation prevents a known error from occurring in the Poisson Accuracy test by commenting the 8th order tests case in the code. This should be reviewed in the future.

Related Issues & Documents

• I have created an Issue that is paired with this PR
• Closes Question about Poisson Accuracy Test #321

QA Instructions, Screenshots, Recordings

Keep-open request

• I am requesting maintainer review for keep-open.

Reason:

Added/updated tests?

_We encourage you to test all code included with MOLE, including examples.

• Yes (this code is a test)
• No, and this is why: please replace this line with details on why tests
  have not been included
• I need help with writing tests

Read Contributing Guide and Code of Conduct

• 📖 I have read the MOLE Contributing Guide: https://github.com/csrc-sdsu/mole/blob/main/CONTRIBUTING.md
• 📖 I have read the MOLE Code of Conduct: https://github.com/csrc-sdsu/mole/blob/main/CODE_OF_CONDUCT.md

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[jbrzensk]

Also, does the test actually run?
@cpaolini pull request was merged, but everything shows as passing?

Is the previous issue fixed?

[Tony-Drummond]

The testPoissonAccuracy.m successfully runs (excluding the case k=8)

[Tony-Drummond]

@jbrzensk there were three different issues, in Issue #361 @Jiya-Rathi reported that the matlab_tests were not even running and the issue had to do with the directory path. This issue was closed with PR #374.

The second issue was related to the 8th order for the testPoissonAccuracy.m tests, which was reported in Issue#321 and that is solved with the PR # 376.

And the last issue, which is still not solved, is why is the GitHub actions not catching the MATLAB errors in the build tests. As you can see above when we run the tests manually, they do failed or run successfully. The former failed cases are not being caught by the build system.

We are now opening a new issue, which will focus on the last issue and tag @cpaolini for help with it.

[Jiya-Rathi]

I have opened the issue mentioned by @Tony-Drummond in issue #377