Re: [E-devel] Exactness integration testing status update
Hello. On 17.07.20 17:06, Stefan Schmidt wrote: Hello. Over the last months we have been working to get exactness testing into state where we can run it during our daily CI tests and cover as much elementary_test test cases as possible. We started with merging it into the efl tree and re-worked quite a bit of its codebase. Including a change to a LD_PRELOAD lib scheme from Marcel. The last week I have been spending now on recording new scenarios for elementary_test cases we had not covered before. We started out with 95 scenarios from and are now at 197. There is still more ground we can cover in the future, but it is a great step forward. In terms of testing code coverage statistics we now have 45.44% (before: 42.99%) with exactness integration tests and ninja unit tests combined. The 1.5% increase was less then we hoped for with all the new additional OK, its almost 2.5%, still less then I hoped for. regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Exactness integration testing status update
Hello. Over the last months we have been working to get exactness testing into state where we can run it during our daily CI tests and cover as much elementary_test test cases as possible. We started with merging it into the efl tree and re-worked quite a bit of its codebase. Including a change to a LD_PRELOAD lib scheme from Marcel. The last week I have been spending now on recording new scenarios for elementary_test cases we had not covered before. We started out with 95 scenarios from and are now at 197. There is still more ground we can cover in the future, but it is a great step forward. In terms of testing code coverage statistics we now have 45.44% (before: 42.99%) with exactness integration tests and ninja unit tests combined. The 1.5% increase was less then we hoped for with all the new additional tests added. It shows that there is a big overlap in the code paths for the two different testing schemes already. To progress this further we need to look into the failing tests cases and see what are bugs in the efl code base, bugs in the test cases (non reproducible tests like time widget with the current time) and what needs extension in exactness (e.g. animation handling comes to mind). I am pretty happy with how far we have progressed with this so far, even if I have hoped for a bigger coverage gain. Still work to do but we can at least enjoy the benefits of it now. regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
