Git commands:
·
git
pull origin main // pull
changes from the remote into your local main
·
git
checkout branchName // switch to an existing branch
·
git
checkout -b branchName //
create and switch to a new branch
·
git
add . // add changes made on the working branch
·
git
commit -m “commit msg” // commit
changes with a meaningful comment
·
git
push origin branchName // push
changes from working branch (PR)
Interfaces:
For lab01 we created an interface class
to represent a generic Shape that has public access modifiers and abstract methods
that will serve as a method blueprint to be overridden within the files that
implement the Shape class file.
Format à public interface Shape {…}
Unit tests:
Created unit tests for both lab00
and lab01 to test the setters and getters, ensuring the data is set and returned
as expected, with the use of asserts and Junit testing. The asserts passes according
to the condition’s return value. For instance, assertNotNull(variable) passes
if the value within returns True, indicating that there is data stored within
that variable, and it is not empty.
Challenges:
Cloning
the repository into IntelliJ. IntelliJ and I have a history of conflicting with
one another, though the experience I gained from using git commands allowed me
to do a workaround by cloning the repository directly via the terminal with
git
clone …
Additionally,
adjusting to the unit test file was a touch of a learning curve, in that it was
necessary to spend time with how the @BeforeAll and @AfterAll sandwich the
individual tests. I can see the future benefits of these annotations for more
complex testing that require a build and or tear down to prevent redundant code.
What went
well:
Working with codingbat exercises. Code is always the most intimidating and being able to practice smaller challenges not only refreshes my syntax knowledge, but built much more confidence is working with strings, arrays, and logic.
No comments:
Post a Comment