https://github.com/chenshaw010/j-unit-testing
Simple application service functionality to facilitate thorough JUnit testing.
https://github.com/chenshaw010/j-unit-testing
java junit junit-test
Last synced: about 1 year ago
JSON representation
Simple application service functionality to facilitate thorough JUnit testing.
- Host: GitHub
- URL: https://github.com/chenshaw010/j-unit-testing
- Owner: CHenshaw010
- Created: 2024-03-30T22:20:12.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-03-30T22:37:49.000Z (about 2 years ago)
- Last Synced: 2025-02-07T22:26:59.671Z (over 1 year ago)
- Topics: java, junit, junit-test
- Language: Java
- Homepage:
- Size: 23.4 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## This Java application provides sample functionality to facilitate JUnit testing.
### Quick Navigation:
Appointment
[Appointment Code](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/AppointmentService/Appointment.java)
[Appointment JUnit Tests](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/AppointmentService/AppointmentTest.java)
[AppointmentService](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/AppointmentService/AppointmentService.java)
[AppointmentService JUnit Tests](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/AppointmentService/AppointmentServiceTest.java)
Contact
[Contact Code](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/ContactService/Contact.java)
[Contact JUnit Tests](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/ContactService/ContactTest.java)
[ContactService](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/ContactService/ContactService.java)
[ContactService JUnit Tests](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/ContactService/ContactServiceTest.java)
Task
[Task Code](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/TaskService/Task.java)
[Task JUnit Tests](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/TaskService/TaskTest.java)
[TaskService](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/TaskService/TaskService.java)
[TaskService JUnit Tests](https://github.com/CHenshaw010/J-Unit-Testing/blob/main/TaskService/TaskServiceTest.java)
### Personal Notes:
- How can I ensure that my code, program, or software is functional and secure?
- There are many techniques necessary to ensure software is functional and secure. It it highly important to review the requirements prior to development so any new development will be tailored to meet the requirements. Next, the code should constantly be compiled and run to ensure no new errors have been introduced or can be addressed early. Reviews of the code should also be conducted to ensure no weaknesses in code syntax exist. Finally, unit testing is paramount to ensure the code is functional. In doing so, the unit tests can be created off the specifications of the requirements. Therefore, if any test fails, the code base does not meet that requirement.
- How do I interpret user needs and incorporate them into a program?
- Communication is key in interpreting user needs. The customer should be available to address any concerns or questions about how to proceed ensuring the software continually meets requirements and gray areas are eliminated. In doing so, the customer will lay out requirements the software must meet, both functional and non-functional. These requirements should be verified by the customer, documented so they can be reviewed, and checked against the codebase at a later date. This processes will ensure the customer's needs have been met and the code functions as intended.
- How do I approach designing software?
- I approach designing software with a methodical approach. First, the requirements must be elicited. From there, any questions can be addressed and any additional information necessary can be obtained. Next, the software can be designed by identifying what will be necessary to meet the requirements. After thorough designing has been done, the code can be written tailored to the requirements. The code should also be frequently compiled and ran ensuring no errors have been introduced. After a unit has been written, it should be examined through unit tests with predefined inputs so the output can also be predetermined. If the output of the code does not match the expected output, the unit should be examined for the reason. These unit test will be written to the specifications of the requirements which means a passed test is a section of code that fulfills the requirements. Once units are integrated, similar integration testing should be conducted ensuring each module can communicate effective. In this whole process, secure coding practices should be utilized to protect data wherever possible. Furthermore, coding standards should be upheld which will enhance the readability and maintainability of the software.