-
Updated
Oct 27, 2018 - Go
unit-test
Here are 720 public repositories matching this topic...
-
Updated
Jul 23, 2020
-
Updated
Oct 7, 2020 - TypeScript
-
Updated
Sep 19, 2020 - Python
-
Updated
Jan 17, 2020 - Java
-
Updated
Sep 11, 2020 - JavaScript
Shell completion
-
Updated
Jan 7, 2020 - Groovy
-
Updated
Aug 22, 2020 - Swift
-
Updated
Feb 23, 2020 - Java
-
Updated
Jun 21, 2019 - Shell
-
Updated
Jun 10, 2018 - JavaScript
-
Updated
Nov 28, 2017 - Kotlin
-
Updated
Jul 25, 2020
-
Updated
Jul 2, 2017 - C++
-
Updated
Jan 2, 2020 - Kotlin
-
Updated
Oct 26, 2019 - Kotlin
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 4, 2020 - C#
-
Updated
Nov 7, 2017 - JavaScript
Improve this page
Add a description, image, and links to the unit-test topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the unit-test topic, visit your repo's landing page and select "manage topics."
I haven't started using the "public" class variables that came along with 3.0 so I'm not sure right now how it would work...but asserting that these properties work or exist should be good.
For example you can just reference
.position
on something instead of usingget_position
orset_position
. I believe these still go through accessors but I haven't made any of these. In my game I'm kee