edhoc 1.3.3 → 2.0.0

package/external/libedhoc/externals/Unity/examples/example_4/test/TestProductionCode.c

@@ -1,70 +0,0 @@
-/* =========================================================================
-    Unity - A Test Framework for C
-    ThrowTheSwitch.org
-    Copyright (c) 2007-24 Mike Karlesky, Mark VanderVoord, & Greg Williams
-    SPDX-License-Identifier: MIT
-========================================================================= */
-
-
-#include "ProductionCode.h"
-#include "unity.h"
-
-/* sometimes you may want to get at local data in a module.
- * for example: If you plan to pass by reference, this could be useful
- * however, it should often be avoided */
-extern int Counter;
-
-void setUp(void)
-{
-  /* This is run before EACH TEST */
-  Counter = 0x5a5a;
-}
-
-void tearDown(void)
-{
-}
-
-
-void test_FindFunction_WhichIsBroken_ShouldReturnZeroIfItemIsNotInList_WhichWorksEvenInOurBrokenCode(void)
-{
-  /* All of these should pass */
-  TEST_ASSERT_EQUAL(0, FindFunction_WhichIsBroken(78));
-  TEST_ASSERT_EQUAL(0, FindFunction_WhichIsBroken(2));
-  TEST_ASSERT_EQUAL(0, FindFunction_WhichIsBroken(33));
-  TEST_ASSERT_EQUAL(0, FindFunction_WhichIsBroken(999));
-  TEST_ASSERT_EQUAL(0, FindFunction_WhichIsBroken(-1));
-}
-
-void test_FindFunction_WhichIsBroken_ShouldReturnTheIndexForItemsInList_WhichWillFailBecauseOurFunctionUnderTestIsBroken(void)
-{
-  /* You should see this line fail in your test summary */
-  TEST_ASSERT_EQUAL(1, FindFunction_WhichIsBroken(34));
-
-  /* Notice the rest of these didn't get a chance to run because the line above failed.
-   * Unit tests abort each test function on the first sign of trouble.
-   * Then NEXT test function runs as normal. */
-  TEST_ASSERT_EQUAL(8, FindFunction_WhichIsBroken(8888));
-}
-
-void test_FunctionWhichReturnsLocalVariable_ShouldReturnTheCurrentCounterValue(void)
-{
-    /* This should be true because setUp set this up for us before this test */
-    TEST_ASSERT_EQUAL_HEX(0x5a5a, FunctionWhichReturnsLocalVariable());
-
-    /* This should be true because we can still change our answer */
-    Counter = 0x1234;
-    TEST_ASSERT_EQUAL_HEX(0x1234, FunctionWhichReturnsLocalVariable());
-}
-
-void test_FunctionWhichReturnsLocalVariable_ShouldReturnTheCurrentCounterValueAgain(void)
-{
-    /* This should be true again because setup was rerun before this test (and after we changed it to 0x1234) */
-    TEST_ASSERT_EQUAL_HEX(0x5a5a, FunctionWhichReturnsLocalVariable());
-}
-
-void test_FunctionWhichReturnsLocalVariable_ShouldReturnCurrentCounter_ButFailsBecauseThisTestIsActuallyFlawed(void)
-{
-    /* Sometimes you get the test wrong.  When that happens, you get a failure too... and a quick look should tell
-     * you what actually happened...which in this case was a failure to setup the initial condition. */
-    TEST_ASSERT_EQUAL_HEX(0x1234, FunctionWhichReturnsLocalVariable());
-}

package/external/libedhoc/externals/Unity/examples/example_4/test/TestProductionCode2.c

@@ -1,42 +0,0 @@
-/* =========================================================================
-    Unity - A Test Framework for C
-    ThrowTheSwitch.org
-    Copyright (c) 2007-24 Mike Karlesky, Mark VanderVoord, & Greg Williams
-    SPDX-License-Identifier: MIT
-========================================================================= */
-
-
-#include "ProductionCode2.h"
-#include "unity.h"
-
-/* These should be ignored because they are commented out in various ways:
-#include "whatever.h" 
-#include "somethingelse.h"
-*/
-
-void setUp(void)
-{
-}
-
-void tearDown(void)
-{
-}
-
-void test_IgnoredTest(void);
-void test_AnotherIgnoredTest(void);
-void test_ThisFunctionHasNotBeenTested_NeedsToBeImplemented(void);
-
-void test_IgnoredTest(void)
-{
-    TEST_IGNORE_MESSAGE("This Test Was Ignored On Purpose");
-}
-
-void test_AnotherIgnoredTest(void)
-{
-    TEST_IGNORE_MESSAGE("These Can Be Useful For Leaving Yourself Notes On What You Need To Do Yet");
-}
-
-void test_ThisFunctionHasNotBeenTested_NeedsToBeImplemented(void)
-{
-    TEST_IGNORE(); /* Like This */
-}

package/external/libedhoc/externals/Unity/examples/example_4/test/test_runners/TestProductionCode2_Runner.c

@@ -1,53 +0,0 @@
-/* AUTOGENERATED FILE. DO NOT EDIT. */
-
-/*=======Test Runner Used To Run Each Test Below=====*/
-#define RUN_TEST(TestFunc, TestLineNum) \
-{ \
-  Unity.CurrentTestName = #TestFunc; \
-  Unity.CurrentTestLineNumber = TestLineNum; \
-  Unity.NumberOfTests++; \
-  if (TEST_PROTECT()) \
-  { \
-      setUp(); \
-      TestFunc(); \
-  } \
-  if (TEST_PROTECT()) \
-  { \
-    tearDown(); \
-  } \
-  UnityConcludeTest(); \
-}
-
-/*=======Automagically Detected Files To Include=====*/
-#include "unity.h"
-#include <setjmp.h>
-#include <stdio.h>
-#include "ProductionCode2.h"
-
-/*=======External Functions This Runner Calls=====*/
-extern void setUp(void);
-extern void tearDown(void);
-extern void test_IgnoredTest(void);
-extern void test_AnotherIgnoredTest(void);
-extern void test_ThisFunctionHasNotBeenTested_NeedsToBeImplemented(void);
-
-
-/*=======Test Reset Option=====*/
-void resetTest(void);
-void resetTest(void)
-{
-  tearDown();
-  setUp();
-}
-
-
-/*=======MAIN=====*/
-int main(void)
-{
-  UnityBegin("test/TestProductionCode2.c");
-  RUN_TEST(test_IgnoredTest, 18);
-  RUN_TEST(test_AnotherIgnoredTest, 23);
-  RUN_TEST(test_ThisFunctionHasNotBeenTested_NeedsToBeImplemented, 28);
-
-  return (UnityEnd());
-}

package/external/libedhoc/externals/Unity/examples/example_4/test/test_runners/TestProductionCode_Runner.c

@@ -1,57 +0,0 @@
-/* AUTOGENERATED FILE. DO NOT EDIT. */
-
-/*=======Test Runner Used To Run Each Test Below=====*/
-#define RUN_TEST(TestFunc, TestLineNum) \
-{ \
-  Unity.CurrentTestName = #TestFunc; \
-  Unity.CurrentTestLineNumber = TestLineNum; \
-  Unity.NumberOfTests++; \
-  if (TEST_PROTECT()) \
-  { \
-      setUp(); \
-      TestFunc(); \
-  } \
-  if (TEST_PROTECT()) \
-  { \
-    tearDown(); \
-  } \
-  UnityConcludeTest(); \
-}
-
-/*=======Automagically Detected Files To Include=====*/
-#include "unity.h"
-#include <setjmp.h>
-#include <stdio.h>
-#include "ProductionCode.h"
-
-/*=======External Functions This Runner Calls=====*/
-extern void setUp(void);
-extern void tearDown(void);
-extern void test_FindFunction_WhichIsBroken_ShouldReturnZeroIfItemIsNotInList_WhichWorksEvenInOurBrokenCode(void);
-extern void test_FindFunction_WhichIsBroken_ShouldReturnTheIndexForItemsInList_WhichWillFailBecauseOurFunctionUnderTestIsBroken(void);
-extern void test_FunctionWhichReturnsLocalVariable_ShouldReturnTheCurrentCounterValue(void);
-extern void test_FunctionWhichReturnsLocalVariable_ShouldReturnTheCurrentCounterValueAgain(void);
-extern void test_FunctionWhichReturnsLocalVariable_ShouldReturnCurrentCounter_ButFailsBecauseThisTestIsActuallyFlawed(void);
-
-
-/*=======Test Reset Option=====*/
-void resetTest(void);
-void resetTest(void)
-{
-  tearDown();
-  setUp();
-}
-
-
-/*=======MAIN=====*/
-int main(void)
-{
-  UnityBegin("test/TestProductionCode.c");
-  RUN_TEST(test_FindFunction_WhichIsBroken_ShouldReturnZeroIfItemIsNotInList_WhichWorksEvenInOurBrokenCode, 20);
-  RUN_TEST(test_FindFunction_WhichIsBroken_ShouldReturnTheIndexForItemsInList_WhichWillFailBecauseOurFunctionUnderTestIsBroken, 30);
-  RUN_TEST(test_FunctionWhichReturnsLocalVariable_ShouldReturnTheCurrentCounterValue, 41);
-  RUN_TEST(test_FunctionWhichReturnsLocalVariable_ShouldReturnTheCurrentCounterValueAgain, 51);
-  RUN_TEST(test_FunctionWhichReturnsLocalVariable_ShouldReturnCurrentCounter_ButFailsBecauseThisTestIsActuallyFlawed, 57);
-
-  return (UnityEnd());
-}

package/external/libedhoc/externals/Unity/examples/unity_config.h

@@ -1,251 +0,0 @@
-/* =========================================================================
-    Unity - A Test Framework for C
-    ThrowTheSwitch.org
-    Copyright (c) 2007-24 Mike Karlesky, Mark VanderVoord, & Greg Williams
-    SPDX-License-Identifier: MIT
-========================================================================= */
-
-/* Unity Configuration
- * As of May 11th, 2016 at ThrowTheSwitch/Unity commit 837c529
- * Update: December 29th, 2016
- * See Also: Unity/docs/UnityConfigurationGuide.pdf
- *
- * Unity is designed to run on almost anything that is targeted by a C compiler.
- * It would be awesome if this could be done with zero configuration. While
- * there are some targets that come close to this dream, it is sadly not
- * universal. It is likely that you are going to need at least a couple of the
- * configuration options described in this document.
- *
- * All of Unity's configuration options are `#defines`. Most of these are simple
- * definitions. A couple are macros with arguments. They live inside the
- * unity_internals.h header file. We don't necessarily recommend opening that
- * file unless you really need to. That file is proof that a cross-platform
- * library is challenging to build. From a more positive perspective, it is also
- * proof that a great deal of complexity can be centralized primarily to one
- * place in order to provide a more consistent and simple experience elsewhere.
- *
- * Using These Options
- * It doesn't matter if you're using a target-specific compiler and a simulator
- * or a native compiler. In either case, you've got a couple choices for
- * configuring these options:
- *
- *  1. Because these options are specified via C defines, you can pass most of
- *     these options to your compiler through command line compiler flags. Even
- *     if you're using an embedded target that forces you to use their
- *     overbearing IDE for all configuration, there will be a place somewhere in
- *     your project to configure defines for your compiler.
- *  2. You can create a custom `unity_config.h` configuration file (present in
- *     your toolchain's search paths). In this file, you will list definitions
- *     and macros specific to your target. All you must do is define
- *     `UNITY_INCLUDE_CONFIG_H` and Unity will rely on `unity_config.h` for any
- *     further definitions it may need.
- */
-
-#ifndef UNITY_CONFIG_H
-#define UNITY_CONFIG_H
-
-/* ************************* AUTOMATIC INTEGER TYPES ***************************
- * C's concept of an integer varies from target to target. The C Standard has
- * rules about the `int` matching the register size of the target
- * microprocessor. It has rules about the `int` and how its size relates to
- * other integer types. An `int` on one target might be 16 bits while on another
- * target it might be 64. There are more specific types in compilers compliant
- * with C99 or later, but that's certainly not every compiler you are likely to
- * encounter. Therefore, Unity has a number of features for helping to adjust
- * itself to match your required integer sizes. It starts off by trying to do it
- * automatically.
- **************************************************************************** */
-
-/* The first attempt to guess your types is to check `limits.h`. Some compilers
- * that don't support `stdint.h` could include `limits.h`. If you don't
- * want Unity to check this file, define this to make it skip the inclusion.
- * Unity looks at UINT_MAX & ULONG_MAX, which were available since C89.
- */
-/* #define UNITY_EXCLUDE_LIMITS_H */
-
-/* The second thing that Unity does to guess your types is check `stdint.h`.
- * This file defines `UINTPTR_MAX`, since C99, that Unity can make use of to
- * learn about your system. It's possible you don't want it to do this or it's
- * possible that your system doesn't support `stdint.h`. If that's the case,
- * you're going to want to define this. That way, Unity will know to skip the
- * inclusion of this file and you won't be left with a compiler error.
- */
-/* #define UNITY_EXCLUDE_STDINT_H */
-
-/* ********************** MANUAL INTEGER TYPE DEFINITION ***********************
- * If you've disabled all of the automatic options above, you're going to have
- * to do the configuration yourself. There are just a handful of defines that
- * you are going to specify if you don't like the defaults.
- **************************************************************************** */
-
- /* Define this to be the number of bits an `int` takes up on your system. The
- * default, if not auto-detected, is 32 bits.
- *
- * Example:
- */
-/* #define UNITY_INT_WIDTH 16 */
-
-/* Define this to be the number of bits a `long` takes up on your system. The
- * default, if not autodetected, is 32 bits. This is used to figure out what
- * kind of 64-bit support your system can handle.  Does it need to specify a
- * `long` or a `long long` to get a 64-bit value. On 16-bit systems, this option
- * is going to be ignored.
- *
- * Example:
- */
-/* #define UNITY_LONG_WIDTH 16 */
-
-/* Define this to be the number of bits a pointer takes up on your system. The
- * default, if not autodetected, is 32-bits. If you're getting ugly compiler
- * warnings about casting from pointers, this is the one to look at.
- *
- * Example:
- */
-/* #define UNITY_POINTER_WIDTH 64 */
-
-/* Unity will automatically include 64-bit support if it auto-detects it, or if
- * your `int`, `long`, or pointer widths are greater than 32-bits. Define this
- * to enable 64-bit support if none of the other options already did it for you.
- * There can be a significant size and speed impact to enabling 64-bit support
- * on small targets, so don't define it if you don't need it.
- */
-/* #define UNITY_SUPPORT_64 */
-
-
-/* *************************** FLOATING POINT TYPES ****************************
- * In the embedded world, it's not uncommon for targets to have no support for
- * floating point operations at all or to have support that is limited to only
- * single precision. We are able to guess integer sizes on the fly because
- * integers are always available in at least one size. Floating point, on the
- * other hand, is sometimes not available at all. Trying to include `float.h` on
- * these platforms would result in an error. This leaves manual configuration as
- * the only option.
- **************************************************************************** */
-
- /* By default, Unity guesses that you will want single precision floating point
-  * support, but not double precision. It's easy to change either of these using
-  * the include and exclude options here. You may include neither, just float,
-  * or both, as suits your needs.
-  */
-/* #define UNITY_EXCLUDE_FLOAT  */
-/* #define UNITY_INCLUDE_DOUBLE */
-/* #define UNITY_EXCLUDE_DOUBLE */
-
-/* For features that are enabled, the following floating point options also
- * become available.
- */
-
-/* Unity aims for as small of a footprint as possible and avoids most standard
- * library calls (some embedded platforms don't have a standard library!).
- * Because of this, its routines for printing integer values are minimalist and
- * hand-coded. To keep Unity universal, though, we eventually chose to develop
- * our own floating point print routines. Still, the display of floating point
- * values during a failure are optional. By default, Unity will print the
- * actual results of floating point assertion failures. So a failed assertion
- * will produce a message like "Expected 4.0 Was 4.25". If you would like less
- * verbose failure messages for floating point assertions, use this option to
- * give a failure message `"Values Not Within Delta"` and trim the binary size.
- */
-/* #define UNITY_EXCLUDE_FLOAT_PRINT */
-
-/* If enabled, Unity assumes you want your `FLOAT` asserts to compare standard C
- * floats. If your compiler supports a specialty floating point type, you can
- * always override this behavior by using this definition.
- *
- * Example:
- */
-/* #define UNITY_FLOAT_TYPE float16_t */
-
-/* If enabled, Unity assumes you want your `DOUBLE` asserts to compare standard
- * C doubles. If you would like to change this, you can specify something else
- * by using this option. For example, defining `UNITY_DOUBLE_TYPE` to `long
- * double` could enable gargantuan floating point types on your 64-bit processor
- * instead of the standard `double`.
- *
- * Example:
- */
-/* #define UNITY_DOUBLE_TYPE long double */
-
-/* If you look up `UNITY_ASSERT_EQUAL_FLOAT` and `UNITY_ASSERT_EQUAL_DOUBLE` as
- * documented in the Unity Assertion Guide, you will learn that they are not
- * really asserting that two values are equal but rather that two values are
- * "close enough" to equal. "Close enough" is controlled by these precision
- * configuration options. If you are working with 32-bit floats and/or 64-bit
- * doubles (the normal on most processors), you should have no need to change
- * these options. They are both set to give you approximately 1 significant bit
- * in either direction. The float precision is 0.00001 while the double is
- * 10^-12. For further details on how this works, see the appendix of the Unity
- * Assertion Guide.
- *
- * Example:
- */
-/* #define UNITY_FLOAT_PRECISION 0.001f  */
-/* #define UNITY_DOUBLE_PRECISION 0.001f */
-
-
-/* *************************** MISCELLANEOUS ***********************************
- * Miscellaneous configuration options for Unity
- **************************************************************************** */
-
-/* Unity uses the stddef.h header included in the C standard library for the
- * "NULL" macro. Define this in order to disable the include of stddef.h. If you
- * do this, you have to make sure to provide your own "NULL" definition.
- */
-/* #define UNITY_EXCLUDE_STDDEF_H */
-
-/* Define this to enable the unity formatted print macro:
- * "TEST_PRINTF"
- */
-/* #define UNITY_INCLUDE_PRINT_FORMATTED */
-
-
-/* *************************** TOOLSET CUSTOMIZATION ***************************
- * In addition to the options listed above, there are a number of other options
- * which will come in handy to customize Unity's behavior for your specific
- * toolchain. It is possible that you may not need to touch any of these but
- * certain platforms, particularly those running in simulators, may need to jump
- * through extra hoops to operate properly. These macros will help in those
- * situations.
- **************************************************************************** */
-
-/* By default, Unity prints its results to `stdout` as it runs. This works
- * perfectly fine in most situations where you are using a native compiler for
- * testing. It works on some simulators as well so long as they have `stdout`
- * routed back to the command line. There are times, however, where the
- * simulator will lack support for dumping results or you will want to route
- * results elsewhere for other reasons. In these cases, you should define the
- * `UNITY_OUTPUT_CHAR` macro. This macro accepts a single character at a time
- * (as an `int`, since this is the parameter type of the standard C `putchar`
- * function most commonly used). You may replace this with whatever function
- * call you like.
- *
- * Example:
- * Say you are forced to run your test suite on an embedded processor with no
- * `stdout` option. You decide to route your test result output to a custom
- * serial `RS232_putc()` function you wrote like thus:
- */
-/* #define UNITY_OUTPUT_CHAR(a)                    RS232_putc(a) */
-/* #define UNITY_OUTPUT_CHAR_HEADER_DECLARATION    RS232_putc(int) */
-/* #define UNITY_OUTPUT_FLUSH()                    RS232_flush() */
-/* #define UNITY_OUTPUT_FLUSH_HEADER_DECLARATION   RS232_flush(void) */
-/* #define UNITY_OUTPUT_START()                    RS232_config(115200,1,8,0) */
-/* #define UNITY_OUTPUT_COMPLETE()                 RS232_close() */
-
-/* Some compilers require a custom attribute to be assigned to pointers, like
- * `near` or `far`. In these cases, you can give Unity a safe default for these
- * by defining this option with the attribute you would like.
- *
- * Example:
- */
-/* #define UNITY_PTR_ATTRIBUTE __attribute__((far)) */
-/* #define UNITY_PTR_ATTRIBUTE near */
-
-/* Print execution time of each test when executed in verbose mode
- *
- * Example:
- *
- * TEST - PASS (10 ms)
- */
-/* #define UNITY_INCLUDE_EXEC_TIME */
-
-#endif /* UNITY_CONFIG_H */

package/external/libedhoc/externals/Unity/extras/bdd/src/unity_bdd.h

@@ -1,44 +0,0 @@
-/* =========================================================================
-    Unity - A Test Framework for C
-    ThrowTheSwitch.org
-    Copyright (c) 2007-24 Mike Karlesky, Mark VanderVoord, & Greg Williams
-    SPDX-License-Identifier: MIT
-========================================================================= */
-
-#ifndef UNITY_BDD_TEST_H_
-#define UNITY_BDD_TEST_H_
-
-#ifdef __cplusplus
-extern "C"
-{
-#endif
-
-#include <stdio.h>
-
-/**
- * @brief Macros for defining a Behavior-Driven Development (BDD) structure with descriptions.
- *
- * These macros provide a way to structure and describe different phases (Given, When, Then) of a
- * test scenario in a BDD-style format. However, they don't have functional behavior by themselves
- * and are used for descriptive purposes.
- */
-#define GIVEN(description) \
-    if (0) { \
-        printf("Given %s\n", description); \
-    } else
-
-#define WHEN(description) \
-    if (0) { \
-        printf("When %s\n", description); \
-    } else
-
-#define THEN(description) \
-    if (0) { \
-        printf("Then %s\n", description); \
-    } else
-
-#ifdef __cplusplus
-}
-#endif
-
-#endif 

package/external/libedhoc/externals/Unity/extras/bdd/test/test_bdd.c

@@ -1,129 +0,0 @@
-/* =========================================================================
-    Unity - A Test Framework for C
-    ThrowTheSwitch.org
-    Copyright (c) 2007-24 Mike Karlesky, Mark VanderVoord, & Greg Williams
-    SPDX-License-Identifier: MIT
-========================================================================= */
-
-#include "unity.h"
-#include "unity_bdd.h"
-
-void test_bdd_logic_test(void) {
-    GIVEN("a valid statement is passed")
-    {
-        // Set up the context
-        bool givenExecuted = true;
-
-        WHEN("a statement is true")
-        {
-            // Perform the login action
-            bool whenExecuted = true;
-            
-            THEN("we validate everything was worked")
-            {
-                // Check the expected outcome
-                bool thenExecuted = true;
-
-                TEST_ASSERT_TRUE(givenExecuted);
-                TEST_ASSERT_TRUE(whenExecuted);
-                TEST_ASSERT_TRUE(thenExecuted);
-            }
-        }
-    }
-} // end of case
-
-void test_bdd_user_account(void) {
-    GIVEN("a user's account with sufficient balance")
-    {
-        // Set up the context
-        float accountBalance = 500.0;
-        float withdrawalAmount = 200.0;
-
-        WHEN("the user requests a withdrawal of $200")
-        {
-            // Perform the withdrawal action
-            if (accountBalance >= withdrawalAmount)
-            {
-                accountBalance -= withdrawalAmount;
-            } // end if
-            THEN("the withdrawal amount should be deducted from the account balance")
-            {
-                // Check the expected outcome
-
-                // Simulate the scenario
-                float compareBalance = 500.0;
-                TEST_ASSERT_LESS_THAN_FLOAT(accountBalance, compareBalance);
-            }
-        }
-    }
-} // end of case
-
-void test_bdd_empty_cart(void) {
-    GIVEN("a user with an empty shopping cart")
-    {
-        // Set up the context
-        int cartItemCount = 0;
-
-        WHEN("the user adds a product to the cart")
-        {
-            // Perform the action of adding a product
-
-            THEN("the cart item count should increase by 1")
-            {
-                // Check the expected outcome
-                cartItemCount++;
-
-                TEST_ASSERT_EQUAL_INT(cartItemCount, 1);
-            }
-        }
-    }
-} // end of case
-
-void test_bdd_valid_login(void) {
-    GIVEN("a registered user with valid credentials")
-    {
-        // Set up the context
-        const char* validUsername = "user123";
-        const char* validPassword = "pass456";
-
-        WHEN("the user provides correct username and password")
-        {
-            // Perform the action of user login
-            const char* inputUsername = "user123";
-            const char* inputPassword = "pass456";
-
-            THEN("the login should be successful")
-            {
-                // Check the expected outcome
-                // Simulate login validation
-                TEST_ASSERT_EQUAL_STRING(inputUsername, validUsername);
-                TEST_ASSERT_EQUAL_STRING(inputPassword, validPassword);
-            }
-        }
-
-        WHEN("the user provides incorrect password")
-        {
-            // Perform the action of user login
-            const char* inputUsername = "user123";
-            const char* inputPassword = "wrongpass";
-
-            THEN("the login should fail with an error message")
-            {
-                // Check the expected outcome
-                // Simulate login validation
-                TEST_ASSERT_EQUAL_STRING(inputUsername, validUsername);
-                // TEST_ASSERT_NOT_EQUAL_STRING(inputPassword, validPassword);
-            }
-        }
-    }
-} // end of case
-
-int main(void)
-{
-    UnityBegin("test_bdd.c");
-    RUN_TEST(test_bdd_logic_test);
-    RUN_TEST(test_bdd_user_account);
-    RUN_TEST(test_bdd_empty_cart);
-    RUN_TEST(test_bdd_valid_login);
-    return UnityEnd();
-}