cs-utulsa / Encrypted-Chat-Service

This is the major project for the year long senior software class. The focus on this repository is to create a encrypted chat service, which can be used for secure communication. It will include not only peer to peer chat services, but also file transfer and group chats.
5 stars 1 forks source link

Testing: Unit Testing #74

Closed tuckplace closed 1 year ago

tuckplace commented 1 year ago

Goal of this story is to complete our sprint specific assignment. Each of us need to complete 3 unit tests and 1 integration test. This is required as part of this sprint by the class.

Each unit test can be small or large. Just pick a small segment of code and ensure it works as intended for each unit test. The integration test also simply needs to ensure different parts work properly together. This could be between two methods or classes. Once you have completed your tests, add writeups of each in a comment on this issue.

EWFranks commented 1 year ago

Unit Test the unit test is procedural, requires the block of code in addition to the next. These were ran in isolation from the chat class. -Ran reading in the file multiple times and all successfully printed the contents of each file to the console. -Ran getFileName from a designated list of files and all returned the correct file name. -Ran fCreateFile and was able create the file with the correct content in a designated location and returned error if wrong. Integration test ran within the chat class -Successfully read in a file and returned its name. Next successfully copying those contents to a specific designated path.

dawsonjones2020 commented 1 year ago

-Tested the three custom message-type widgets to make sure they stayed formatted in different-sized windows and messages -Tested the main screen frames on different sizes and settings to make sure they rendered properly -Tested the message box frame to make sure overloading the text box wouldn't result in an error

piangno commented 1 year ago

-Test 1: connect() method on the App class. It should prompt a message box to decide for client and server. Everything work as expected, there are more implementations needed in the method which should be done in the future sprint. -Test 2: connect() method from the client side. The client attempts to connect with the server 5 times. Tested with correct and incorrect inputs(ip and port). It work as expected so far. -Test 3: on_closing() method on the App class. The program should with all the connections. It closed as expected.

mypleasure370 commented 1 year ago

Specifics will be in documentation shortly :)