summaryrefslogtreecommitdiff
path: root/sc/CppunitTest_sc_tableautoformatfield.mk
AgeCommit message (Collapse)AuthorFilesLines
2012-08-21add more runtime deps on resource files for unit-testsMatúš Kukan1-5/+0
Change-Id: Id9bbb2bbcafe335eada3f36ae103a9074a56848f
2012-08-10gbuild: missing dep on $(OUTDIR)/unittest/registry for testsMatúš Kukan1-3/+1
Change-Id: Ic80f57946e7b3f9c1bd99ed65955cf3c280063d2
2012-04-12move dependency on localedata_en to i18npoolMatúš Kukan1-4/+1
2012-04-08rename gb_CppunitTest_uses_ureDavid Tardon1-1/+1
2012-04-08compile- and run-time use of UNO must be splitDavid Tardon1-0/+2
There are unit tests that do not use URE, e.g., in cppuhelper. This reverts commit 33e9f3d3d6b29545ef9df3f5334c015e15caa5c8. Conflicts: sot/CppunitTest_sot_test_sot.mk svl/CppunitTest_svl_urihelper.mk
2012-04-08clean upDavid Tardon1-2/+1
2012-04-08simplify use of configuration from unit testsDavid Tardon1-3/+6
2012-04-08always use --protector for UNO testsDavid Tardon1-1/+0
2012-04-08drop uses_ureDavid Tardon1-2/+0
2012-04-08let use_api handle the use of type rdbs at runtimeDavid Tardon1-4/+0
Or is there any use case where we would need to use UNO API headers, but not require the appropriate type database at runtime?
2012-04-08gbuild: "use" vs. "add":Michael Stahl1-4/+4
Naming convention for gbuild methods: - "add" is used for stuff that is logically a part of the target (i.e. not registered at the Module, but defined in the target's makefile) - "use" is used for stuff that is logically a different target (i.e. it is registered at the Module, has it's own makefile, may be in a different module than the target)
2012-04-02always pass --headless to cppunitsLuboš Luňák1-1/+0
They should not need any actual UI anyway, and most of them already pass the option manually. http://lists.freedesktop.org/archives/libreoffice/2012-March/029109.html
2012-03-10gbuild: get rid of realpath in gb_Foo_set_includeMatúš Kukan1-2/+2
2012-02-10fdo#39491 -I$(OUTDIR)/inc is set in SOLARINCMatúš Kukan1-1/+0
2012-01-23add library for c++ based subsequenttestsMarkus Mohrhard1-0/+1
use this library for interface tests and implement the test in the correct module by creating one test class per implementation class The implementation class should inherit from all interface tests it needs This should make it more easy to write tests since we no longer need to write the same test method multiple times
2012-01-15these are not old component files anymoreMatúš Kukan1-6/+3
2011-12-19Tests apparently depend on localedata_en library.Stephan Bergmann1-1/+4
More tests might be affected. Also unclear to me whether it is always (only) localedata_en, or whether it could also be _es/_euro/_others.
2011-12-14configmgr.component is no longer an old one.Stephan Bergmann1-1/+1
2011-12-06Moved modifications.xcu to test, used from multiple modules.Stephan Bergmann1-1/+1
2011-12-05add subsequent test for failing test TableAutoFormatFieldMarkus Mohrhard1-0/+141
tests are still disabled but problem is related to 7da57d17b6179e71c8b6d7549ad89eaf3a4a28c6