#33 50% of FB/Function will need a Unit Test

1.0.0.0: EoN
wont-fix
aliazzz
None
2020-10-18
2020-06-20
aliazzz
No

Unit test will be written to cover 50% of the FB's and methods from the library using Cfunit v1.1.0.0 or better.
The unittest project in the trunk is to be leading. Any other tests can be written in branches to test personal developments.
As the trunk of the library gets updated, ideally the unittest project of the trunk gets updated too.

The software will be unit tested and/or integration tested, as much as possible.

My suggestion is that we all take a peek at the unit test code whenever we feel like it to ensure that it passes a basic sanity level

Discussion

  • aliazzz

    aliazzz - 2020-07-24
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -2,16 +2,9 @@
 The unittest project in the trunk is to be leading. Any other tests can be written in branches to test personal developments.
 As the trunk of the library gets updated, ideally the unittest project of the trunk gets updated too. 

-The following software will be unit tested and/or integration tested
-~~~
-    FB_MQTT_PubSub
-    FB_EoN_Node
-    FB_Payload
-    FB_SparkplugB
-~~~
+The software will be unit tested and/or integration tested, as much as possible.

-FB_Payload is a Test Driven Development (TDD) candidate as it exceeds in complexity.
-Updates wil follow.
+**My suggestion is that we all take a peek at the unit test code whenever we feel like it to ensure that it passes a basic sanity level**
     

  • i-campbell

    i-campbell - 2020-09-16
    • Milestone: MVP EoN --> 1.0.0.0: EoN
     

  • i-campbell

    i-campbell - 2020-10-12
    • summary: Every FB/Function will need a mandatory Unit Test. --> 50% of FB/Function will need a Unit Test
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,6 +1,6 @@
-Unit test will be written for each of the FB's from the library using Cfunit v10.9.95 (RC5) or better.
+Unit test will be written to cover 50% of the FB's and methods from the library using Cfunit v1.1.0.0 or better.
 The unittest project in the trunk is to be leading. Any other tests can be written in branches to test personal developments.
-As the trunk of the library gets updated, ideally the unittest project of the trunk gets updated too. 
+As the trunk of the library gets updated, ideally the unittest project of the trunk gets updated too.

 The software will be unit tested and/or integration tested, as much as possible.
     

  • i-campbell

    i-campbell - 2020-10-12

    90% test coverage moved to standard product milestone

     

  • i-campbell

    i-campbell - 2020-10-18
    • status: pending --> wont-fix
     

  • i-campbell

    i-campbell - 2020-10-18

    Won't Fix reason: Moved to 2.0.0.0, see #74

     

Log in to post a comment.