Comments (2)
Why do you need this??? FeatureContext just defines a hooks and step definitions. That's all! Why do you want multiple copies of same steps in your suite? It doesn't makes sense to me. It's impossible by couple of reasons and most important one is that Behat will not be able to resolve what definition to use, when he'll have multiple contexts with exact same step definitions (inheritance). Another reason is that every FeatureContext defines loadable hooks and Behat can have multiple - multiple contexts will load multiple hooks at a time.
FeatureContext is just a code representation of your features - step definitions and hooks. And i don't see why you might need multiple classes, that'll provide same information (even if we forgot, that Behat not able do handle them anyway).
To use main context steps - use context aliases:
$this->getMainContext()->visit(...);
from behat.
oh ok thanks for explaining I thought i could not use mink shortcuts on subcontexts due to this impossibility
now I am a bit more clear on the code too, thanks a lot @everzet !
from behat.
Related Issues (20)
- Suite hooks defined with Attributes not working HOT 3
- Transformations have no attribute to define them
- Skip a scenario entirely based on @BeforeScenario HOT 4
- SSL certificate problem: unable to get local issuer certificate HOT 3
- Symfony 7 support HOT 1
- [bug] jUnit formatter returns time as int but should use float HOT 1
- [Bug] jUnit formatter produces empty testsuite names, it could use feature file as suite name HOT 5
- Parallelization of tests HOT 1
- SigintController does not check for both pcntl-functions used in execute() HOT 6
- [Bug?] Reruns of Scenario outlines lead to potentially confusing scenario names HOT 2
- Exception thrown when test fails with junit formatter HOT 1
- Documentation for StepEvent hooks in Behat 3.0 HOT 8
- Add support for Rule keyword (Gherkin 6) HOT 2
- Skip or improve translation process
- how to have a context/class per feature ?
- New release for Symfony 7 HOT 8
- Can't use %paths.base% inside extensions: Failed opening required '%paths.base%' HOT 2
- phar is broken for the 3.14.0 release HOT 4
- Extension for auto naming parameters HOT 2
- Better documentation for `filters` key
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from behat.