So in #codeception in #php the `#[Group('abc')]` is completely different from the `groups:` config in yml? One is test groups and the other is "tests grouped in folders.
And you can't disable a test group by default, only via CLI param...
WTF, bro?
So in #codeception in #php the `#[Group('abc')]` is completely different from the `groups:` config in yml? One is test groups and the other is "tests grouped in folders.
And you can't disable a test group by default, only via CLI param...
WTF, bro?
Has anyone manages to get out a #codeception remote #coverage (selenium) report different from 0. I have an #yii2 #php app and after 2h of struggle I made run but c3 reports 0lines coverage...
🧪 New set of tests for #rosariosis
18 new programs of RosarioSIS are now tested with #codeception through acceptance tests.
Acceptance testing is browser automation to check the app works correctly, just like a user would do by clicking buttons, filling fields, etc...
https://gitlab.com/francoisjacquet/rosariosis-meta/#codeception
#codeception docs say the "RunFailed" extension is enabled by default since version 2+ but dumping the config actually proves the opposite. May be I'm somehow overriding some defaults or may be they mean with the "default configuration file".
Все тесты — это юнит тесты :o
Немного веселья на серьезную тему правильного нейминга тестов и 100500 их типов и видов. Обязательно дочитай до конца, иначе пропустишь невероятно мудрый посыл ;)
https://habr.com/ru/articles/820247/
#phpunit #codeception #интеграционное_тестирование #модульное_тестирование #unit_test
TIL: Codeceptions `::wantTo("xyz")` is evaluated at parsing time, not at runtime.
Means, you can't use variables or expressions in the argument. Now that was funny to discover...
If the generated FunctionalTester would at least keep the method docblocks, so IDE would have the doc directly available, that would've been faster to find.
Trying to find a straightforward way to merge XML coverage reports generated by #phpunit via #CodeCeption. The end goal is a nice HTML report. I can generate the HTML report or XML for a single chunk, but none of the tooling I can find to combine the chunks works. There's an open bug in #phpcov which prevents the serialized PHP reports from being able to be combined.
I'd consider tools in php, python, node, rust, or binaries for mac or linux.
Does anyone have a go to solution?
Anybody already testing self-written APIs with Codeception? (Trying to explore the codeception REST module for #craftcms https://github.com/craftcms/cms/discussions/10284 🤔) #testing #php #codeception #ddev
Has anyone made #yii2 and #codeception unit tests work with no actual DB without mocking objects and etc? I know Laravel can fake it well and I haven't tried Symfony on this, TBH. The current solution (still decent) is it shoves all data changes in a transaction that gets cancelled at the end of a test. Still imperfect as all auto-increment values stay. We use a shared dev DB... don't ask...
I released Codeception 5.0.11
https://github.com/Codeception/Codeception/releases/tag/5.0.11
#codeception #release
Running #codeception on a #PHP >=8.1 project?
Don't do a full composer update, latest #phpunit 10.x is incompatible with current codeception, due to changes in internal API:
After crossbrowsertesting phasing over to bitbar, I've tried and evaluated browserstack, lambdatest and a few other similar tools. I did end up with a runner up Sauce labs, primarily due to better(for me) pricemodel. #browsertesting #codeception #laravel #symfony
When I need to do this kind of refactoring:
https://gitlab.com/johanv/1jg/-/merge_requests/10/diffs
I'm glad that I use value objects for identifiers, and that I have static analysis and automatic tests. #php #1jg #phpstan #codeception
Can anybody try to explain to me what I need #codeception for? From my perspective it has no real advantages over using #PHPUnit with a few additional libraries. It just introduces more code that might fail or be unsupported in the future, requires quite a lot of boilerplate and there are probably far less developers knowing codeception than PHPUnit. And acception testing can be done with either of those, I don't see much value added here as well.
New Year, New Versions
#roboParacept #codeception #PHP
https://github.com/Codeception/robo-paracept/releases/tag/3.1.0
https://github.com/Codeception/robo-paracept/releases/tag/2.1.2
https://github.com/Codeception/robo-paracept/releases/tag/2.0.3
https://github.com/Codeception/robo-paracept/releases/tag/1.3.3
The Workshop: Accept testing with Codeception - php[architect] Magazine April 2022
Finally found a way to run #Codeception tests and generate coverage with Github actions
If you can’t test your legacy system than start with acceptance tests. You don’t must know the complex structure at start but you must be sure that everything is running after you have change something 😊🫣 #codeception #php #acceptance
Next Release published of #roboParacept
Helpful for Users which already use #codeception Version 5 but with PHP 8.0
https://github.com/Codeception/robo-paracept/releases/tag/2.1.0
Short news:
#PHP8 or above is required
consolidation/robo Version 4
For more info pls check the Changelog
I’m happy to tweet that codeception/robo-paracept has reached the version 3.0.0
It supports now the newest #codeception with version 5.0
It requires the newest #PHP Version 8.1 and #robo 4.0
For more details check https://github.com/Codeception/robo-paracept/releases/tag/3.0.0