[SOLVED] Cs6300 individual project: edittxt deliverable 2 fall2025

This part of the document is provided to help you track where you are in the individual project. This section will be updated in future deliverables.

Provided

Expected

Provided

Expected

Provided: TBD

Expected: TBD

Provided: TBD

Expected: TBD

In this deliverable, we will assume that someone else in your company implemented the edittxt utility while you were creating test cases for it. For the sake of the assignment, we will also assume that your colleague is an infallible developer and produced a flawless implementation. Consequently, all the test cases you created for Deliverable 1 (D1) are supposed to pass on this implementation.

To complete this deliverable, you will submit your test cases (i.e., class MyMainTest) and make sure that they pass on the reference implementation, which will be hidden from you. Gradescope will run them for you and report information about passing and failing tests. You may have to modify some of your tests, or add or delete tests from the tests submitted in D1. You will not be penalized for this, and you do not need to modify your category-partition files accordingly. Note that we are expecting the test class MyMainTest to be self-contained; that is, your tests should not rely on any external classes or resources.

Your grade for this deliverable will be the average of three parts:

Extra credit: If (1) all of your tests pass on the correct reference implementation, (2) your tests cover all of our representative scenarios, and (3) all of your tests fail on the faulty reference implementation, you will get 10 extra points, for a total of 110 points (for this deliverable). There is no partial credit for this assignment; you must meet all three previous requirements to get the extra credit for this deliverable.

The tests you submitted for D1 should be able to pass all the checks and be graded, so it may be worth doing an initial submission right away, as a sanity check. Moreover, it could be the case that all of your test cases are already passing on the correct reference implementation, failing on the buggy reference implementation, and covering enough scenarios, in which case you would be done with the mandatory part of the deliverable.

While the autograder provides details on which of your test cases fail on the reference code, it only reports the number of scenarios that your tests do not cover. To improve that part of your score, you will have to consider the program domain again and try to identify cases you may be missing. We cannot provide hints on what scenarios your test suite does not cover.

Following are the steps to commit and submit this deliverable:

javac -cp lib/* -d classes src/edu/gatech/seclass/edittxt/*.java test/edu/gatech/seclass/edittxt/*.java^[1]

java -cp classes:lib/* org.junit.platform.console.ConsoleLauncher –select-class edu.gatech.seclass.edittxt.MyMainTest^[2]

submission.txt

As soon as you submit, Gradescope will grade your submission by:

If any of the above steps fail, you will see a grade of 0 and an error message with some diagnostic information. Please note that, as before, if your submission does not pass the Gradescope checks, it will receive a 0. Conversely, if Gradescope can successfully compile and run your code and tests, you will immediately receive a grade that is your actual grade for this deliverable. Note that you can resubmit as many times as you want before the deadline.

Unlike other assignments, this deliverable is not available to be submitted on Gradescope until the previous deliverable is due. That is, deliverable 2 will be available on Gradescope 48 hours after this assignment is released on Canvas.

The test results you see in Gradescope tell you whether a given test passed or not. If the test didn’t pass, Gradescope should show the difference between the expected and actual output.

As stated in the Grade section, Gradescope will show your score will be calculated based on

Student tests passing on CORRECT reference code: X/Y

where X is the number of tests passing on the correct reference code and Y is the total number of tests you designed. All tests must pass on this implementation, so X should be equal to Y.

Student tests passing on FAULTY reference code: Z/Y

where Z is the number of tests passing on the faulty reference implementation and Y is the total number of tests you designed. All tests must fail on this implementation (since this implementation is incorrect), so Z should be 0.

Coverage achieved: <percentage achieved>% (W/T)

where W is the amount of scenarios your test suite uncovered, T is the total number of coverage scenarios we designed, and percentage achieved is the percentage representation of W/T.

If you need clarifications on a specific test or Gradescope output, please post privately on Ed Discussion (if appropriate, we will make it public) and make sure to add, when applicable:

The bottom line is that, to make the interaction efficient, you should make your posts as self-contained and easy-to-check as possible. The faster we can respond to the posts, the more students we can help. Although we tested the autograder, it may still handle some corner cases incorrectly. If you receive feedback that seems to be incorrect, please contact us on Ed Discussion using the approach we describe above.

Answer: Yes, this shouldn’t result in an error and does not change any behavior. This will keep the lines containing the given substring “-i”. This happens because we parse first, so “-i” becomes the parameter for “-k”, just like any other string.

Answer: Yes, you can update the catpart, although it will not be graded.

Answer: We cannot reveal any of the scenarios tested against.

^[1] On some platforms, you may need to first create directory “classes”.

^[2] If using a Windows-based system, you may need to run
java -cp “classes;lib/*” org.junit.platform.console.ConsoleLauncher
–select-class edu.gatech.seclass.edittxt.MyMainTest