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

Update documentation to reflect new namespace heirarchy #97

Merged
merged 1 commit into from
Nov 16, 2019
Merged

Update documentation to reflect new namespace heirarchy #97

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/teaching/grading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ If you run the test under the "Grader" config, you can run just the grading scri
This assumes that you are running inside the gradescope docker container.

```
sbt "Grader / testOnly dinocpu.LabXGrader"
sbt "Grader / testOnly dinocpu.test.grader.LabXGrader"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine for now... we might want to try to find a way to make this easier for students.

```

See [run_autograder](run_autograder) for more details.
Expand Down
10 changes: 5 additions & 5 deletions documentation/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ To run one suite, use `testOnly` instead of `test`.
For instance, to run just the ALU Control tests you can use the following.

```
sbt:dinocpu> testOnly dinocpu.ALUControlTester
sbt:dinocpu> testOnly dinocpu.test.components.ALUControlTester
```

Note: You can use tab completion in sbt to make searching for tests easier.
Expand Down Expand Up @@ -98,7 +98,7 @@ You can search in "should match expectations for each instruction type" (ignore
So, let's say you only want to run the single cycle CPU test which executes the `add1` application, you can use the following.

```
sbt:dinocpu> testOnly dinocpu.SingleCycleCPUTester -- -z add1
sbt:dinocpu> testOnly dinocpu.test.SingleCycleCPUTester -- -z add1
```

## CPU Test Case
Expand Down Expand Up @@ -188,9 +188,9 @@ In the CPUTestCase below, we run the binary `add2`, which is compiled from `add2

Simply copying the CPU Test case as is and adding in changes to register values will throw the error show below.
```
sbt:dinocpu> testOnly dinocpu.SingleCycleCPUTester -- -z add
sbt:dinocpu> testOnly dinocpu.test.SingleCycleCPUTester -- -z add
[info] SingleCycleCPUTester:
[info] dinocpu.SingleCycleCPUTester *** ABORTED ***
[info] dinocpu.test.SingleCycleCPUTester *** ABORTED ***
[info] Duplicate test name: Single Cycle CPU should run rtype add2 (CPUTests.scala:27)
[info] ScalaTest
[info] Run completed in 411 milliseconds.
Expand All @@ -200,7 +200,7 @@ In the CPUTestCase below, we run the binary `add2`, which is compiled from `add2
[info] *** 1 SUITE ABORTED ***
[error] Error: Total 1, Failed 0, Errors 1, Passed 0
[error] Error during tests:
[error] dinocpu.SingleCycleCPUTester
[error] dinocpu.test.SingleCycleCPUTester
[error] (Test / testOnly) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 3 s, completed Jan 14, 2019 6:29:23 AM

Expand Down