Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
Sorry, no photos available for this element of time.
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
Media Name | File Type | Date | Description | |
wayne_intro_into_unit_testing.mp4 | Video | 12/5/2019 | Training meeting lead by Wayne. Introduction to unit testing. |
Notes:
|
Wayne lead out the training session. We had Alan, Bryan, Dustin, Josh, Wayne, Brandon, and Steve on the meeting. - From Wayne - focusing on the process vs just the code. Strive for test driven design. - Going step by step vs trying to design the whole thing at once. - Currently, we all do testing as we are building the new code or features. The test driven design process leaves a virtual trail (crumb trail) of what was done and what was tested. That becomes very valuable as the processes get more and more complicated. - It may take awhile longer on the frontend, but over time, you will save time and be able to have more confidence in your code and subsequence changes later on. - We went through a number of test options. As a side note, Wayne spent some time making sure that we know that we can create mock datasets and be able to fake the results. - Unit testing and making sure you are testing the smallest unit of that function. Be specific. See attached for a link to the video recording. |