acassis commented on code in PR #3260:
URL: https://github.com/apache/nuttx-apps/pull/3260#discussion_r2639783286


##########
testing/nest/nest_main.c:
##########
@@ -0,0 +1,105 @@
+/****************************************************************************
+ * apps/testing/nest/nest_main.c
+ *
+ * SPDX-License-Identifier: Apache-2.0
+ *
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.  The
+ * ASF licenses this file to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
+ * License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  See the
+ * License for the specific language governing permissions and limitations
+ * under the License.
+ *
+ ****************************************************************************/
+
+/****************************************************************************
+ * Included Files
+ ****************************************************************************/
+
+#include <nuttx/config.h>
+
+#include <stdio.h>
+
+#include <testing/unity.h>
+
+#include "nest.h"
+
+/****************************************************************************
+ * Pre-processor Definitions
+ ****************************************************************************/
+
+/****************************************************************************
+ * Private Data
+ ****************************************************************************/
+
+/****************************************************************************
+ * Private Functions
+ ****************************************************************************/
+
+/****************************************************************************
+ * Public Functions
+ ****************************************************************************/
+
+/****************************************************************************
+ * Name: setUp
+ *
+ * Description:
+ *   Unity required set up function. Not used.
+ ****************************************************************************/
+
+void setUp(void)
+{
+  /* Intentionally empty */
+
+  return;
+}
+
+/****************************************************************************
+ * Name: tearDown
+ *
+ * Description:
+ *   Unity required tear down function. Not used.
+ ****************************************************************************/
+
+void tearDown(void)
+{
+  /* Intentionally empty */
+
+  return;
+}
+
+/****************************************************************************
+ * nest_main
+ ****************************************************************************/
+
+int main(int argc, FAR char **argv)
+{
+  UNUSED(argc);
+  UNUSED(argv);
+
+  UNITY_BEGIN();

Review Comment:
   @linguini1 Amazing!!!
   
   Question: is it possible to associate a Unique ID for each test and have a 
verbose (human understing) message about the test?
   
   Of course it should be optional (in the Kconfig) because could add overhead 
(more text message in the firmware), but should be useful to have a high level 
understanding of what was tested, i.e.:
   
   ```
   0001: "Circular Buffer Initialization"       => PASSED
   0002: "Circular Buffer Memory Allocation"  => PASSED
   0003: "Circular Buffer Memory Released"   => PASSED
   ...
   0049: "Driver zerodev Read/Write Testing" => PASSED
   ```
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to