1f08c3bdfSopenharmony_ciBOUNDARY TESTS 2f08c3bdfSopenharmony_ci============== 3f08c3bdfSopenharmony_ciIt is sometimes useful to test parameter boundaries as part of API testing. 4f08c3bdfSopenharmony_ciIn the POSIX Test Suite Framework, variables cannot be assigned to values that 5f08c3bdfSopenharmony_ciwould cause warnings (because warnings are treated as errors), so the following 6f08c3bdfSopenharmony_cilist of boundary values has been created for boundary testing. 7f08c3bdfSopenharmony_ci 8f08c3bdfSopenharmony_ciThese boundary values are those values that the gcc compiler would set an 9f08c3bdfSopenharmony_ciinvalid parameter to during compile time: 10f08c3bdfSopenharmony_ci 11f08c3bdfSopenharmony_ciINT32_MAX+1 -2147483647 (gcc compiler gave -2147483648) 12f08c3bdfSopenharmony_ciINT32_MIN-1 2147483647 13f08c3bdfSopenharmony_ciunassigned val -1073743192 14f08c3bdfSopenharmony_ciunassigned val 1075002478 15f08c3bdfSopenharmony_ci 16f08c3bdfSopenharmony_ciPotentially the MAX+1/MIN-1 values are deterministic. The others are just 17f08c3bdfSopenharmony_ciempirical examples. 18f08c3bdfSopenharmony_ci 19f08c3bdfSopenharmony_ciContributors: julie.n.fleischer REMOVE-THIS AT intel DOT com 20f08c3bdfSopenharmony_ci geoffrey.r.gustafson REMOVE-THIS AT intel DOT com 21