path: root/src/tests/ecore/ecore_test_ecore.c (follow)
AgeCommit message (Collapse)Author
2019-10-24tests/ecore: unset app args after app args unit test to prevent invalid readsMike Blumenkrantz
Summary: various internal components in efl access the app args and read them which will result in invalid memory access since these are stack-allocated strings Depends on D10412 Subscribers: cedric, #reviewers, #committers Tags: #efl Differential Revision:
2019-07-25tests/ecore: verify that quit() -> begin() does not pre-cancel main loopMike Blumenkrantz
Summary: ref 17f433c57bfa11319a22fde1aedb21e99a3a1268 Reviewers: cedric Reviewed By: cedric Subscribers: cedric, #reviewers, #committers Tags: #efl Differential Revision:
2019-06-20tests: fix warnings and undef ref on Windows (using meson :-) )Vincent Torri
Summary: we need to include evil_private.h so that some symbols are declared Test Plan: compilation Reviewers: raster, zmike, cedric Subscribers: #reviewers, #committers Tags: #efl Differential Revision:
2018-04-10tests: split ecore poller tests into separate fileMike Blumenkrantz
Summary: ref T6850 Depends on D5900 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6850 Differential Revision:
2018-04-10tests: split ecore idler tests into separate fileMike Blumenkrantz
Summary: ref T6850 Depends on D5899 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6850 Differential Revision:
2018-04-10tests: move efl_loop_fd tests into efl_app_suiteMike Blumenkrantz
Summary: ref T6815 Depends on D5898 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6815 Differential Revision:
2018-04-10tests: move ecore_test_ecore_main_loop_timer into timers test fileMike Blumenkrantz
Summary: Depends on D5892 Reviewers: stefan_schmidt Subscribers: cedric Differential Revision:
2018-04-10tests: reduce duration of ecore_test_ecore_main_loop_timer testMike Blumenkrantz
Summary: fix T6852 Depends on D5890 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6852 Differential Revision:
2018-04-10tests: use 0.05s as poller interval in ecore_test_ecore_main_loop_pollerMike Blumenkrantz
Summary: fix T6852 Depends on D5883 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6852 Differential Revision:
2018-04-10tests: split ecore_test_ecore_main_loop_poller_add_del into separate testsMike Blumenkrantz
Summary: unit tests should verify only small pieces of functionality to ensure that they are testing what they claim to be testing fix T6852 Depends on D5882 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6852 Differential Revision:
2018-04-05tests: move to using checked fixtures for all test suitesMike Blumenkrantz
individual tests should not need to explicitly call init/shutdown functions in most cases, and many did not properly do this anyway see followup commit which resolves some issues with eina tests ref T6813 ref T6811 Reviewed-by: Stefan Schmidt <>
2018-04-05tests: add instrumentation to existing tests to find slow testsMike Blumenkrantz
efl_check.h must be included and the EFL_START/END_TEST macros must be used in place of normal START/END_TEST macros timing is enabled when TIMING_ENABLED is set Reviewed-by: Stefan Schmidt <>
2018-03-03put efl app test back with mods to match app as superclassCarsten Haitzler (Rasterman)
2018-03-03ecore - a different take on class as a super class to efl.loopCarsten Haitzler (Rasterman)
so the MAIN loop is actually an object. which inherits from efl.loop. the idea is that other loops in threads will not be objects. thread on the creator side return an efl.thread object. inside the thread, like the mainloop, there is now an efl.appthread object that is for all non-main-loop threads. every thread (main loop or child) when it spawns a thread is the parent. there are i/o pipes from parnet to child and back. so parents are generally expected to, if they want to talk to child thread, so use the interfaces on efl.thread, and the main loop's class allows you to talk to stdio back to the parent process like the efl.appthread does the same using the interfaces to talk to its parent app or appthread. it's symmetrical no tests here - sure. i have been holding off on tests until things settle. that's why i haven't done them yet. those will come back in a subsequent commit for really quick examples on using this see: they are just my test code for this. Please see this design document:
2018-03-03Revert "cxx: Fix manual code after efl_app change."Carsten Haitzler (Rasterman)
This reverts commit 135154303bea691c6f7f9472a5dec32d9103c38d. Revert "efl: move signal events from efl.loop to" This reverts commit 3dbca39f98288580c62a43c179ac11621433ec88. Revert "efl: add test suite for efl_app" This reverts commit 3e94be5d73256a7f5c02d3a9474173226be7beff. Revert "efl: create Efl.App class, the parent of Efl.Loop" This reverts commit 28fe00b94e55575c15684959b89a614d5a579309. Go back to before because I think this should be done with superclassing here not a parent object. reasons? 1. multiple loops per single thread make no sense. so if multilpe loop objects they wont be contained in a single app object and then deleted like this. 2. the app object is not really sharable in this design so it cant be accessed from other threads 3. it makes it harder to get the main loop or app object (well 2 func calls one calling the other and more typing. it is longer to type and more work where it is not necessary, and again it can't work from other threads unless we go duplicating per thread and then what is the point of splittyign out the signal events from efl.loop then?) etc.
2018-02-26efl: add test suite for efl_appMike Blumenkrantz
this moves existing tests out of the ecore suite and into a new one, adds some checks to verify loop object parenting, and verifies compile for Efl_Core.h and Efl_Net.h using EFL_NOLEGACY_API_SUPPORT
2018-02-26efl: create Efl.App class, the parent of Efl.LoopMike Blumenkrantz
2018-01-31ecore_event: Check for the valid typeMyoungwoon Roy, Kim
Summary: This patch checks for the valid types. As mentioned API reference documentation, user must know its type before hand. The type should be chedked like previous efl version and ecore_event_type_flush_internal() Test Plan: Execute a ecore test suite. Reviewers: cedric, raster, jpeg, stefan_schmidt, Jaehyun_Cho Subscribers: cedric Differential Revision:
2018-01-31ecore_main: Check for the valid flagMyoungwoon Roy, Kim
Summary: This patch checks for the valid Ecore_Fd_Handler_Flags. The flags should be checked like previous verion because There are no default handlings in case of out of Ecore_Fd_Handler enum values in other funcs. Test Plan: Execute a test case Reviewers: cedric, raster, jpeg, stefan, Jaehyun_Cho Differential Revision:
2018-01-02efl loop - rename ecore_main_loop_get to efl_main_loop_getCarsten Haitzler (Rasterman)
ecore_main_loop_get() is really a new "eo api" but it's using our old ecore_* namespace, so move to the new efl namespace.
2017-12-19ecore: Fix up some test casesJean-Philippe Andre
- Add missing ecore_shutdown - Reinstate supposedly silly test case (see previous commits, the main loop object can in fact die cleanly). - Disable really silly test cases (inner main loops aren't meant to work)
2017-12-15tests - disable loop fd and timer lifecycle testsCarsten Haitzler (Rasterman)
these tests assume we delete the loop object on shutdown which we are not doing atm as it's a lot of trouble... and frankly of little value.
2017-12-15tests - ecore suite - dont shadow a global var - use different oneCarsten Haitzler (Rasterman)
2017-02-02ecore: implement new requirement in the test suite.Cedric BAIL
2016-09-05Rename efl_self to efl_addedTom Hacohen
It has been discussed on the ML (thread: "[RFC] rename efl_self") and IRC, and has been decided we should rename it to this in order to avoid confusion with the already established meaning of self which is very similar to what we were using it for, but didn't have complete overlap. Kudos to Marcel Hollerbach for initiating the discussion and fighting for it until he convinced a significant mass. :) This commit breaks API, and depending on compiler potentially ABI. @feature
2016-08-30Efl object: Rename Eo_Event -> Efl_Event.Tom Hacohen
This is the last step of the Eo renaming efforts.
2016-08-15Eo: Finish the renaming of Eo to the EFL.Tom Hacohen
This renames all the rest of the API to the EFL namespace except for Eo_Event that will follow soon. Obviously breaks both API and ABI.
2016-08-11Change the EFL to follow the new Eo rename.Tom Hacohen
2016-07-29tests: ecore: try to keep constness for Efl_VersionStefan Schmidt
It returns as const so better try to keep this be having the avriable const as well.
2016-06-29ecore: Add basic test case for efl versionJean-Philippe Andre
Not very useful test but still good to make sure we preserve the API.
2016-06-22ecore: add test for registered provider.Cedric BAIL
2016-06-20Adjust the code according to the eo event stop changes.Tom Hacohen
This was changed in the previous commit.
2016-06-06ecore: make sure lifecycle of Efl.Loop.Fd is correct.Cedric BAIL
2016-05-06ecore: add tests case for Efl.Loop.Fd.Cedric BAIL
2015-12-23efl-js: JavaScript Eolian bindingFelipe Magno de Almeida
To configure efl sources with bindings to use in nodejs add ––with-js=nodejs in configure flags to generate node files $ configure --with-js=nodejs and compile normally with: $ make $ make install To use, you have to require efl: efl = require('efl') The bindings is divided in two parts: generated and manually written. The generation uses the Eolian library for parsing Eo files and generate C++ code that is compiled against V8 interpreter library to create a efl.node file that can be required in a node.js instance. @feature
2015-10-31ecore: add test case for idler enterer functionVivek Ellur
Summary: Added test case for ecore_idle_enterer_before_add function Signed-off-by: Vivek Ellur <> Reviewers: cedric Subscribers: cedric Differential Revision: Signed-off-by: Cedric BAIL <>
2013-12-23ecore: fix shutdown when using system module.Cedric BAIL
This patch will detect how many more times ecore_init was called during initialization and use that as a threshold to do a clean shutdown. It is a necessary evil as we do have ecore module that will initialize eldbus that will then reinit ecore_init from within ecore_init and without a chance for the application to act on it. I also reenable a test to make sure we will catch earlier this kind of issue.
2013-12-23ecore: fix tests to avoid failure on successful initialization.Cedric BAIL
This patch is necessary to work around the fact that if you have some ecore system module installed, they will be initialized and may use another library like eldbus that will call ecore_init again. So ecore_init will be different from 1, but still be a success. My patch does introduce a work around a problem in that situation. Calling ecore_shutdown wont work at this stage, as we do have module that did initialize ecore also. And the only way to make ecore_shutdown happen is to unload those module and that wont happen as they where initialized from inside ecore... lala ! Yes, we never shutdown ecore properly when we have ecore module that use something like eldbus.
2013-04-19ecore: update ecore_test_ecore_main_loop_event test for more coverage code.Valerii Kanunik
Signed-off-by: Cedric Bail <>
2013-04-12ecore: add tests for ecore_poll module.Valerii Kanunik
Signed-off-by: Cedric Bail <>
2013-04-12ecore: Added tests for ecore_app_args procedures.Valerii Kanunik
Signed-off-by: Cedric Bail <>
2012-12-03Ecore: merge unit tests, ignore++Vincent Torri
SVN revision: 80090