Using File Service in daemon environment:

========================================

1) Start daemon (nota-ind -m)

2) Start Resource Manager

   - Executable can be found from rm/service/ directory.

   - Start RM (nota-rmsvc)

3) Start File Service

   - Executable can be found from /fs/src/ directory.

   Start FS (nota_fssvc)

4) File Service API can be used for file access.

   e.g. File Service tester application can be started (fs/test/). 

   The following test tries to create new_file.txt file in /foo/bar/ directory.

   ./tester -Cu /foo/bar/new_file.txt

Nota that File Service API should be used with FS stub. FS stub header files are

located in fs/fs_stub/ directory.

The ontology name and description of File Service can be found from 

/fs/fs_stub/common/fileservice.h file. Use these names when asking the Service 

ID of File Service from Resource Manager.

File Service API header file is located in /fs/fs_stub/posix/user/ directory. 

Include the CFSAdapter_user.h file to be able to use File Service stub 

functions.

The generating of branch coverage report about File Service tests:

=================================================================

Coverage is enabled with --enable-coverage flag to configure script. It is recommended 

that possible old files are cleaned with command 'make clean_coverage'. Command 'make clean all' 

cleans binary files and forces coverage support files to be generated.

1) fs$ ./configure --enable-coverage (terminal 1)

   => output includes: CFLAGS ... -fprofile-arcs -ftest-coverage ...

      IF fprofile-arcs and ftest_coverage are missing, the branch 

         coverage does not work.

      => correction: run the following command

      fs$ CFLAGS="-g -02 -fprofile-arcs -ftest-coverage" ./configure

2) fs$ make clean_coverage clean all (terminal 1)

After the branch coverage configurations have been done, the testforfileservice.sh

can be run.

3) fs/test$ sh testforfileservice.sh (terminal 2)

   and waiting the question and instructions

The branch coverage report can be generated by hand as well:

===========================================================

1) same as above (terminal 1)

2) same as above (terminal 1)

3) run tests by hand (terminal 2) e.g.

   fs/test$NOTA_IN_DAEMON=/tmp/nota-test-1 ./tester -Cfu /tmp/exam.txt

   fs/test$NOTA_IN_DAEMON=/tmp/nota-test-1 ./tester -Wu /tmp/exam.txt

   fs/test$NOTA_IN_DAEMON=/tmp/nota-test-1 ./tester -Ru /tmp/exam.txt -l 10

   fs/test$NOTA_IN_DAEMON=/tmp/nota-test-1 ./tester -Dfu /tmp/exam.txt

4) stop file service server (terminal 1) by writing x<enter>

after this generate the branch coverage report

gcov results

------------

There is a script file to help getting results of coverage run. It requires a directory where to

store the results as a parameter. The rest of the parameters will be passed to the actual

gcov call as parameters.

5) fs$ ./coverage.sh gcov_result (terminal 1)

or for more detail

5) fs$ ./coverage.sh gcov_result -b (terminal 1)

6) fs$ cd gcov_result&&more results

OR

lcov results (in HTML format)

-----------------------------

lcov_coverage.sh script file helps getting results of coverage run in HTML format. It requires a 

directory where to store the results as a parameter.

5) fs$ ./lcov_coverage.sh lcov_result

6) fs$ cd lcov_result

7) open index.html with html browser (i.e. file:///<absolute path>/fs/lcov_result/index.html)