aboutsummaryrefslogtreecommitdiffstats
path: root/trial/java/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* Align to jaulib 1.3.3: Full cmake-presets usage w/ vscode support update; ↵v3.3.3Sven Göthel2024-08-091-0/+2
| | | | | | | | | | also use cmake target_{link|compile}_options instead of globals Example run scripts were also adopted. Unit and trial tests passed on amd64 machine. VSCode(ium) IDE integration manually tested.
* Build Environment: Better CMake Usage incl. Eclipse (IDE) default CDT CMake; ↵Sven Göthel2024-05-071-1/+1
| | | | | | | Default is C++20 now (analog to jaulib) Further: - Java Trial: Use native libs from build (not install dist dir), avoid install requirement
* cmake trial launch: Use `-E` for sudo to pass environmentSven Gothel2022-07-071-1/+1
|
* Trial Unit Test C++: Working State; Completed dbt_client_server1x.cpp ...Sven Gothel2022-05-031-1/+1
| | | | | | | | | | | | | | | | | | | | | Native trials match the java trial. Passed native and java tests alike, i.e. may fail w/ BT5 on SC0 or SC1 if no keys are delivered (known issue). Add counting successful protocol sessions next to the total, client determined and send to server via GattCmd. protocolSessionCount allows multiple connection and protocol sessions within one instance, which allows for further stability and leak (valgrind) testing later on. Each tests class's 1st test uses 1 protocolSession, where the 2nd test uses 2 protocolSessions. timeout is detected by the waiting loop thread. max_connection per protocolSession is 5 and shall help with analyzing the known BT5 lack of key delivery. Further renamed the test class numbers to match the test suffix number better.
* Trial testing: Since we don't use jaulib-fat native libs, we shall also not ↵Sven Gothel2022-04-241-2/+2
| | | | use its initialization -> Use jaulib_base and jaulib_test only
* Run java trial w/o fat-jar package but dedicated native lib path to support ↵Sven Gothel2022-04-181-2/+1
| | | | gdb core dump debugging to locate the native libraries
* Fix trial/java/CMakeLists.txt: Use proper environment variable USER for ↵v2.6.0Sven Gothel2022-02-071-1/+1
| | | | capsh command
* Added online unit testing using actual BT adapter, testing client with ↵Sven Gothel2022-02-071-0/+39
server functionality Building with enabled *trial* and *testing* , i.e. live testing with 2 Bluetooth adapter is provided via the *cmake* build argument `-DBUILD_TRIAL=ON`, see above. The *trial* tests utilize one or more actual Bluetooth adapter, hence using the *capsh* launch for the required permissions as described above. Therefor, *sudo* will be called and a user interaction to enter the *sudo* password may occur. The *trial* tests cover *Direct-BT*'s Bluetooth functionality, having its *master/client* and *slave/server peripheral* facilities communicating via actual adapter, supporting regression testing of the API, its implementation and adapter.