Refiners coverage report

Hi all,
I would like to know how can I create a report based on the refiners coverage.
For example, I want to know how many values exists for one category in relation with all crawled items.
- 100.000 items crawled
- Category = MetadataField
Value1 = 45.457
Value2 = 21.332
Value3 = 14.356
ValueN = 784
NoValue = 1.538
All these values represent in fact the counts which exists in Refinement Panel.
However, there is no refiner value for items which have NoValue. (How can we include this, in order to appear in Refinement Panel?)
Many thanks for any ideea.
OvidiuG

Hi,
Why dont you use MD06, this report gives the coverage based on requirements. The report can be read by MRP controller or Vendor or Product Group.
I am sure it shoudl meet the need, instead of going for a Z report, unless there are some additional requirements.
Hope the above helps.
Regards,
Vivek

Similar Messages

Need info on Coverage reports which supports spring 2.0 framework

I want to know whether there is Coverage report tool which is an eclipse plugin and which support Spring 2.0 framework.
Also, whether Coverlipse version supports Spring 2.0?

Spring provides some base classes for easily testing
application code that is wired with spring. It has
things like running tests inside individual
transactions, loading context files, etc.
The last time I tried Coverlipse you could not use
Spring's test case base classes and have the tests
run. That's what is meant by it does not support
Spring.
AaronInteresting. That's not a problem I'd considered. Do you know why this is? Does Coverclipse only measure classes which directly subclass org.junit.TestCase or something? I don't know how Coverclipse works, but don't you just point it at your tests and say "go forth and measure"?
We use JCoverage, and it seems to cope just fine with our tests, hardly any of which actually directly extend TestCase, and probably 3000 of extend a Spring test class. We use Spring 1.2.7, mind you, but I do know another team using the same build process as us, and it JCoverage works just fine with their Spring 2.0-based tests. I can't really see why a coverage tool wouldn't work with Spring test classes, or their helpers, since as long as they're on the classpath, they can be loaded and used. Is the Coverclipse classpath configured properly? Don't rely on it picking up it's classpath from your project, not all plugin authors think of that. Wouldn't surprise me if the plugin simply didn't have Spring 2.0 on it's classpath

Could any one teel me how to see coverage report for core1_mini regression

Hi every one:
I would like to see coverage report for core1_mini regression with vcs. I used the follow command:
sims -sim_type=vcs -vcs_build -vcs_use_cm -vcs_cm_args="line+cond+fsm+tgl" -group=core1_mini.
After simulation, 4 files have been generated:
cm_data.line,cm_data.cond,cm_data.fsm,cm_data.tgl.
(under /coverage/verilog)
Are these four file for all tests(mini regression 68 tests totally)?
Is it true? shall I moify somewhere in sims,1.262 ,for example vcs_cm_merge? I feel a little confussed.
Thanks in advance!

If Remote wipe is activated it can't be undone. And Once the Wipe is done, the device can nö longer be tracked.
Sorry.

[svn] 2785: update clover code coverage report, add tests for asc commandline arguments

Revision: 2785
Author: [email protected]
Date: 2008-08-08 09:56:23 -0700 (Fri, 08 Aug 2008)
Log Message:
update clover code coverage report, add tests for asc commandline arguments
Modified Paths:
flex/sdk/trunk/modules/asc/build/java/build.xml
flex/sdk/trunk/modules/asc/test/compiler/runtests.py
flex/sdk/trunk/modules/asc/test/compiler/testconfig.txt
Added Paths:
flex/sdk/trunk/modules/asc/test/compiler/cmdline/
flex/sdk/trunk/modules/asc/test/compiler/cmdline/abcfuture.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtarget.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtarget.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtargetn.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtargetn.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/config.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/config.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/exe.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/exe.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help1.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help1.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help2.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help2.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/m.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/metadata.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/movieclip.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/sanity.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/sanity.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_bytes.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_flow.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_flow.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_instructions.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_parse_trees.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_parse_trees.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/static_semantics.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/static_semantics.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/swf.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/swf.err

Poor coverage report

Duplicate post - Poor coverage report - Englewood, CO
Message was edited by: Admin Moderator

Your signal can be affected by anything from foliage to building structure. Most people tend to have the most problem in the Spring and Summer months due to foliage. Once Fall arrives, you'll see your signal typically gets a bit better.
That said, which phone do you use? Some phones have been affected negatively by the the Android KitKat 4.4.2 update.

Coverage Html Report

Hello,
Please forgive my poor English.
I use Oracle SQL Developer 3.0 Early Adopter 2.
I　hope for Coverage Report(e.g. JUnit , Cobertura) to be maked.
The quality is sure to go up if the mechanism of Coverage Report can be done.
Thank you.

As of v2.x, you can use the internal Unit Tests. RTM.
Anything else you can request this at the SQL Developer Exchange though, so other users can vote and add weight for possible future implementation.
Regards,
K.

How to view the emma coverage test result when running local job

Hi Guys,
When using emma in DTE, we can obtain the code coverage test result. I submit a farm job, and can get a txt or html file on coverage report. But when I run it locally, the txt / html files is unavailable. I can only see a folder named coverage with coverage.emma & metadata.emma. So my question is how can I get the coverage report from it?
If I can use some command to generate report files, then what is it and how to run it.
Thanks

Hello Twenz
This forum is mainly (should not be only but it is) used for supporting Oracle Application Testing Suite (OATS) products.
I guess your question is not related to this solution at all. So maybe this is not really the right forum.
Good luck
JB

Standard SAP Planning reports

Hi all
I have a requirement for some planning reports and I am hoping to find them in standard ECC.
Can anyone let me know if they are aware of what is available to meet the following;
Coverage reports or shorage reports at the component level
Waterfall reporting
thanks

Hi
Did you try CO09 or MD46?
Kindly revert back

Reports Required in MM

Dear SAP Experts,
My Client is required as follows report in MM. We have to tell input to technofunctional consultants. Accordingly give me the necessary inputs to get these reports in SAP MM.
1) Consumption report, date to date, & Group & Item wise Summary report (TOTAL OF QTY & VALUE CONSUMED)
2) Inventory range of coverage report (No of days inventory)
3) Inventory comprensive report, ( Opening , Purchase, issue, closing) individual storage location wise & all storage location wise
4) Inventory Ageing report ( item wise, Qty, Value, last purchase date, last issue date, no of days)
5) Physical inventory & Varience report.
Thanks n regards,
Babu

1) Consumption report, date to date, & Group & Item wise Summary report (TOTAL OF QTY & VALUE CONSUMED)
Look to transaction code "MB51, with Movement type
2) Inventory range of coverage report (No of days inventory)
MB5B
3) Inventory comprensive report, ( Opening , Purchase, issue, closing) individual storage location wise & all storage location wise
ME2M,ME2L, ME2N
4) Inventory Ageing report ( item wise, Qty, Value, last purchase date, last issue date, no of days)
MC46,MC50
5) Physical inventory & Varience report.
MI20, MIDO,MI24
These are standard report , you can develop report based on client requirement.

Code coverage using command line always produces a binary file nearly full of zeros, not workable by Visual

I'm using Professional Edition 2013. I try to generate a coverage report for a C project, using the command line interface.
In Visual, configuration of the Linker : Configuration Properties -> Linker -> Advanced -> Profile.
Then:
vsinstr.exe my.exe /COVERAGE
I've got messages from Visual that the instrumentation went well.
VSPerfCmd.exe /START:COVERAGE /OUTPUT:my.coverage
my.exe
VSPerfCmd.exe /SHUTDOWN
The my.coverage file is created. But it's a binary file, more or less full of zeros. Dropping it into Visual just opens it as a binary file. Full stop.
I've tried the same commands on very different .exe files and it seems like the my.coverage file has always the same content.
What am I doing wrong ?
Thx

Hi Fred35,
If you test it with other language project, how about the result? For example, a console app or winform app.
Reference:
http://www.codeproject.com/Articles/590346/CodeplusCoverageplusforplusRegressionplusTestsplus
Based on your description, I think the steps have no issue like this blog here:
http://blogs.msdn.com/b/cellfish/archive/2008/11/16/native-c-code-coverage-reports-using-visual-studio-2008-team-system.aspx
So I'm afraid that we would think about others. Maybe it is the dependent dll file issue.
http://stackoverflow.com/questions/17867591/code-coverage-in-visual-studio-2010-for-native-c-exe-dll
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Attributes / Variable assignment in Excel

How do you create a variable assignment in Excel that passes the "test script coverage" report?
We thought we were being clever when we put a list of our variable assignments in Excel. This allowed us to sort the assignments (something we could not do in Word.)
Our process in Excel:
We put an empty cell in the top row with the "OPM - Condition Heading" style.
In the rows underneath that, we put our attributes with the "OPM - Conclusion Heading" style.
To the right of the attributes, we put the assigned values with the "OPM - Conclusion" style.
We had our nicely sortable list of variables and assignments. It looks cool and works quite well.
However, test coverage analysis reports conclude that we have not tested the attributes since we didn't test for the "uncertain" path. Of course, our variables can never be "uncertain"! To some degree, the test coverage report is wrong, but I understand that the generated rule is an if-then-else rule and not a straight assignment...
Thoughts? Is there a better way to do the variable assignment in Excel? Should we just live with it? Should we create a mock test with all our variables overridden to be "uncertain" or should we do something else?

Sorry for the very late reply here, but I'm afraid the structure you have created is just not well handled by the coverage analysis because it compiles into a rule with an unreachable condition. This is normally harmless but the coverage analysis isn't smart enough to ignore it. I've raised a bug (OPAD-7096) to track this in our internal system.

Getting all salary changes

Hi all,
I need to track all salary changes to send a benefit coverage report to our insurance company.
I've tried a couple of things, but since there are many ways the benefit coverage can be affected, there always some changes I don't get.
The latest I've tried looks like this:
-Using PNP I first eliminated all employees without a infotype 0001 or 0008.
-I'm checking last changes in 0015, 0008 and 0168, if there's something I extract the info.
The only way I succeeded in tracking ALL salary changes was to calculate the salary for each day of the report period and check the preceeding day for a change. This is OK for one employee buy WAY TO SLOW for all our 1350 employee!!.
So any help would be greatly appreciated.

Finally I stick with my first solution to check the salary for each days of the period. With some tuning it is now OK.

Installing libunity and dirty rm

I can't seem to install libunity from source...
==> Continue building libunity ? [Y/n]
==> ----------------------------------
==>
==> Building and installing package
==> Making package: libunity 6.12.0-1 (Sun Dec 2 23:17:26 WET 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found libunity-6.12.0.tar.gz
==> Validating source files with md5sums...
libunity-6.12.0.tar.gz ... Passed
==> Extracting Sources...
-> Extracting libunity-6.12.0.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for valac... /usr/local/bin/valac
checking /usr/local/bin/valac is at least version 0.16.0... yes
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for gobject-introspection m4 macros... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gobject-introspection... yes
checking whether NLS is requested... yes
checking for intltool >= 0.40.0... 0.50.2 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.16.2
checking for XML::Parser... ok
checking for GLIB2... yes
checking for GOBJECT2... yes
checking for GIO2... yes
checking for GIO_UNIX2... yes
checking for GEE... yes
checking for DEE... yes
checking for DBUSMENU... yes
checking for GTK3... yes
checking for GMODULE... yes
checking for glib-compile-resources... /usr/local/bin/glib-compile-resources
checking for glib-mkenums... /usr/local/bin/glib-mkenums
checking for glib-genmarshal... /usr/local/bin/glib-genmarshal
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
configure: creating ./config.status
config.status: creating unity.pc
config.status: creating unity-protocol-private.pc
config.status: creating Makefile
config.status: creating bindings/Makefile
config.status: creating bindings/python/Makefile
config.status: creating data/com.canonical.Unity.Lenses.gschema.xml.in
config.status: creating data/Makefile
config.status: creating doc/Makefile
config.status: creating doc/reference/Makefile
config.status: creating examples/Makefile
config.status: creating po/Makefile.in
config.status: creating protocol/Makefile
config.status: creating src/Makefile
config.status: creating tools/Makefile
config.status: creating test/Makefile
config.status: creating test/C/Makefile
config.status: creating test/vala/Makefile
config.status: creating vapi/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing po/stamp-it commands
configure:
libunity v6.12.0 (soname 9:2:0)
(protocol soname 0:0:0)
Build environment
Prefix : /usr
Build GI typelib : yes
Documentation : no
C warnings : no
Trace logging : no
Testing
Integration tests : no
Headless tests : no
Coverage reporting : no
make all-recursive
make[1]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0'
Making all in data
make[2]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/data'
ITMRG com.canonical.Unity.Lenses.gschema.xml
GEN com.canonical.Unity.Lenses.gschema.valid
make[2]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/data'
Making all in protocol
make[2]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/protocol'
GEN libunity_protocol_private_la_vala.stamp
make all-am
make[3]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/protocol'
CC libunity_protocol_private_la-protocol-icon.lo
CC libunity_protocol_private_la-protocol-lens-interface.lo
CC libunity_protocol_private_la-protocol-scope-interface.lo
CC libunity_protocol_private_la-protocol-previews.lo
CCLD libunity-protocol-private.la
make[3]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/protocol'
make[2]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/protocol'
Making all in src
make[2]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/src'
GEN libunity_la_vala.stamp
unity-scope-proxy-remote.vala:332.7-332.19: warning: implicit .begin is deprecated
unity-scope-proxy-remote.vala:179.9-179.24: warning: implicit .begin is deprecated
unity-scope-proxy-remote.vala:181.9-181.29: warning: implicit .begin is deprecated
unity-scope-proxy-remote.vala:60.36-60.48: warning: implicit .begin is deprecated
unity-scope-private.vala:519.11-519.23: warning: implicit .begin is deprecated
unity-scope-private.vala:521.11-521.23: warning: implicit .begin is deprecated
unity-lens-private.vala:461.5-461.25: warning: implicit .begin is deprecated
unity-sound-menu-mpris.vala:213.9-213.62: warning: implicit .begin is deprecated
unity-lens-private.vala:574.5-574.64: warning: unreachable code detected
return new HashTable<string, Variant> (str_hash, str_equal);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Compilation succeeded - 9 warning(s)
make all-am
make[3]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/src'
CC libunity_la-unity-trace.lo
CC libunity_la-unity-appinfo-manager.lo
CC libunity_la-unity-icon.lo
CC libunity_la-unity-inspector.lo
CC libunity_la-unity-io.lo
CC libunity_la-unity-launcher.lo
CC libunity_la-unity-lens.lo
CC libunity_la-unity-lens-activation.lo
CC libunity_la-unity-lens-category.lo
CC libunity_la-unity-lens-filters.lo
CC libunity_la-unity-lens-merge-strategy.lo
CC libunity_la-unity-lens-preferences-manager.lo
CC libunity_la-unity-lens-private.lo
CC libunity_la-unity-lens-search.lo
CC libunity_la-unity-lens-tools.lo
CC libunity_la-unity-previews.lo
CC libunity_la-unity-scope.lo
CC libunity_la-unity-scope-factory.lo
CC libunity_la-unity-scope-private.lo
CC libunity_la-unity-scope-proxy.lo
CC libunity_la-unity-scope-proxy-local.lo
CC libunity_la-unity-scope-proxy-remote.lo
CC libunity_la-unity-sound-menu.lo
CC libunity_la-unity-sound-menu-mpris.lo
CCLD libunity.la
GEN unity.deps
GICOMP Unity-6.0.gir
Unity-6.0.gir:205:81: warning: element annotation from state 9 is unknown, ignoring
Unity-6.0.gir:1096:70: warning: element annotation from state 9 is unknown, ignoring
Unity-6.0.gir:1156:50: warning: element annotation from state 9 is unknown, ignoring
Unity-6.0.gir:1852:76: warning: element annotation from state 9 is unknown, ignoring
Unity-6.0.gir:2020:52: warning: element annotation from state 9 is unknown, ignoring
make[3]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/src'
make[2]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/src'
Making all in bindings
make[2]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/bindings'
Making all in python
make[3]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/bindings/python'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/bindings/python'
make[3]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/bindings'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/bindings'
make[2]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/bindings'
Making all in tools
make[2]: Entering directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/tools'
GEN unity-tool-res.c
/usr/local/bin/glib-compile-resources: error while loading shared libraries: libffi.so.5: cannot open shared object file: No such file or directory
make[2]: *** [unity-tool-res.c] Error 127
make[2]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0/tools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-david/aur-libunity/src/libunity-6.12.0'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build libunity.
==> Restart building libunity ? [y/N]
==> ---------------------------------
==>
I have libffi installed and glib2 too. I never built glib2 from source, but I have glib stuff on /usr/local/include and /usr/local/bin. I tried downloading glib2 sources, ./autogen.sh and then "make uninstall" but that didn't fix the problem.
So I tried the "dirty way" with "rm /usr/local/bin/glib-compile-resources" and it worked.
I know I probably didn't do this the right way. What would have been the right way and what should I do now to fix it?

Munchor wrote: What would have been the right way and what should I do now to fix it?
Progress on Unity under Arch Linux!
libunity in AUR
AUR on the wiki
And other relevant documentation.
Last edited by Mr.Elendig (2012-12-04 13:07:39)

Automated Unit Tests through NWDI / Purpose of testrun.xml

Hello,
I could not find any documentation on the test infrastructure / system that seems to be integrated into Netweaver CE 7.1. A DC offers the option via the context menu to "Add/Repair Unit Test Support". When this is used the Developer Studio automatically creates the necessary test source folder, JUnit library dependencies and a file called TEST-INF/testrun.xml.
The first two things are clear, but what function does the testrun.xml file serve? To me it looks like it defines the Tests that should be executed (automaticaly during build?). However, the tests are never actually run.
<?xml version="1.0" encoding="UTF-8"?>
<test>
<run type="junit">
<include>com.sap.**</include>
<exclude></exclude>
</run>
</test>
Can anybody expain how this file is though to be used? Or how to perform automatic unit tests during/after the build process?
Thanks in advance.
ciao,
Elmar
Edited by: Elmar Weber on Sep 17, 2008 9:58 AM

Hi test developers,
the integration of JUnit tests into the DC build is planned for 7.30. You can add your tests in a separate test folder and specify additional "test"-dependencies, if required. The tests will be executed during the DC build. If a test fails, the build will also fail. Generation of code coverage reports will be possible, too.
Best Regards,
Jochen Ehret.

Error setting up as an extendeder

Trying to extend my time capsule network by using a new airport express.iI get two error messages: 1. Unable to extend network,check password and range.2.Can't find my network. Everything is working fine,ipad,iphone,etc... Any suggestions?

Open AirPort Utility - Select the Time Capsule - Click Manual Setup
Click the Wireless tab below the row of icons
Make sure that you have enabled the option to "Allow this network to be extended". (Otherwise, the AirPort Expess cannot be configured correctly to extend the network)
Update to save any changes and give the Time Capsule 30-35 seconds to restart
Perform a Factory Default Reset on the AirPort Express (AX) as follows:
Pull the AX from power
Wait a moment or two
Hold in the reset button and keep holding it in for an additional 8-10 seconds while you plug the AX back in to power. You wil see the amber light begin to blink more quickly during this process
Release the reset button and allow 40-45 seconds for the AX to restart to a slow, blinking amber light
Temporarily, connect an Ethernet cable from your computer to the AX and move the AX to the same room or an adjacent room as the Time Capsule
Open AirPort Utility - Select the AX - Click Manual Setup
Click the Base Station tab below the icons to name the AX, establish a device password and adjust Time Zone settings
Click the Wireless tab next to the Base Station tab
Wireless Mode = Extend a wireless network
Wireless Network Name = Same name as the Time Capsule network
Check mark next to "Allow wireless clients"
Wireless Security = Same setting (probably WPA2 Personal) as the Time Capsule
Wireless Password = Same password as the Time Capsule network
Confirm Password
Click Update to save settings
As soon as you see the message that the settings have been stored, close AirPort Utility immediately and disconnect the Ethernet cable
You should have a green light on the AX in 40-45 seconds
Unplug the AX and move it to a location that is approximately half the distance from the Time Capsule to area that needs more wireless coverage
Report on your results

Refiners coverage report

Similar Messages

Maybe you are looking for