Ttdfjt

Does putting salt first make it easier for attacker to bruteforce the hash?

Breaking changes to eieio in Emacs 27?

Multiband vertical antenna not working as expected

Confused with atmospheric pressure equals plastic balloon’s inner pressure

The origin of the Russian proverb about two hares

How durable are silver inlays on a blade?

Can there be absolute velocity?

YA book about blind creatures that live underground and take kid's eyes

Why would a home insurer offer a discount based on credit score?

Print "N NE E SE S SW W NW"

Trying to get (more) accurate readings from thermistor (electronics, math, and code inside)

Proving that a Russian cryptographic standard is too structured

A life of PhD: is it feasible?

Do empty drive bays need to be filled?

Why did the World Bank set the global poverty line at $1.90?

What is the Leave No Trace way to dispose of coffee grounds?

What do you call the action of "describing events as they happen" like sports anchors do?

noalign caused by multirow and colors

Assigning function to function pointer, const argument correctness?

NUL delimited variable

What should I be wary of when insurer is taking a lot of time to decide whether car is repairable or a total loss?

Part of my house is inexplicably gone

Why is the length of the Kelvin unit of temperature equal to that of the Celsius unit?

Why isn't Bash trap working if output is redirected to stdout?

Can @magentoDataFixture files be inside the module itself and not on default directory dev/tests/integration/testsuite?

Creating Integration Tests for Magento 2 Modules

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

4

1

A very good thing about Magento 2 is that we put together all files inside the module itself. Layout XML, Templates, Less/Sass, Blocks, Models, Helpers, API, SQL scripts and everything. It's important because when we enable, disable or even delete the module everything lays on a single directory.

However, when I add a @magentoDataFixture for an integration test, it says it should be placed on dev/tests/integration/testsuite directory, and not on the module itself. The more directories, the more difficult to maintain. It looks like M1 with app and skin directories where files became very far away from each other, in terms of tree directory.

Example:

/**
 * @magentoDataFixture MyNamespace/MyModule/_files/create_some_data_here.php
 */
class CustomIntegrationTestTest extends AbstractController
{

Magento will look up on the directory:
dev/tests/integration/testsuite/MyNamespace/MyModule/_files/create_some_data_here.php

and not somewhere like this:
app/code/MyNamespace/MyModule/Test/....../_files/create_some_data_here.php

Can @magentoDataFixture files be inside the module itself and not on default directory dev/tests/integration/testsuite?

magento2 testing phpunit integration-test

share|improve this question

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  magento.stackexchange.com/questions/93422/…
  
  – Fabian Schmengler
  Jun 4 at 11:44
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  (however you may want to take a look into github.com/tddwizard/magento2-fixtures for an object oriented fixture approach instead of procedural spaghetti scripts)
  
  – Fabian Schmengler
  Jun 4 at 11:45
  

  
  
  
  

add a comment | 

4

1

A very good thing about Magento 2 is that we put together all files inside the module itself. Layout XML, Templates, Less/Sass, Blocks, Models, Helpers, API, SQL scripts and everything. It's important because when we enable, disable or even delete the module everything lays on a single directory.

However, when I add a @magentoDataFixture for an integration test, it says it should be placed on dev/tests/integration/testsuite directory, and not on the module itself. The more directories, the more difficult to maintain. It looks like M1 with app and skin directories where files became very far away from each other, in terms of tree directory.

Example:

/**
 * @magentoDataFixture MyNamespace/MyModule/_files/create_some_data_here.php
 */
class CustomIntegrationTestTest extends AbstractController
{

Magento will look up on the directory:
dev/tests/integration/testsuite/MyNamespace/MyModule/_files/create_some_data_here.php

and not somewhere like this:
app/code/MyNamespace/MyModule/Test/....../_files/create_some_data_here.php

Can @magentoDataFixture files be inside the module itself and not on default directory dev/tests/integration/testsuite?

magento2 testing phpunit integration-test

share|improve this question

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  magento.stackexchange.com/questions/93422/…
  
  – Fabian Schmengler
  Jun 4 at 11:44
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  (however you may want to take a look into github.com/tddwizard/magento2-fixtures for an object oriented fixture approach instead of procedural spaghetti scripts)
  
  – Fabian Schmengler
  Jun 4 at 11:45
  

  
  
  
  

add a comment | 

A very good thing about Magento 2 is that we put together all files inside the module itself. Layout XML, Templates, Less/Sass, Blocks, Models, Helpers, API, SQL scripts and everything. It's important because when we enable, disable or even delete the module everything lays on a single directory.

However, when I add a @magentoDataFixture for an integration test, it says it should be placed on dev/tests/integration/testsuite directory, and not on the module itself. The more directories, the more difficult to maintain. It looks like M1 with app and skin directories where files became very far away from each other, in terms of tree directory.

Example:

/**
 * @magentoDataFixture MyNamespace/MyModule/_files/create_some_data_here.php
 */
class CustomIntegrationTestTest extends AbstractController
{

Magento will look up on the directory:
dev/tests/integration/testsuite/MyNamespace/MyModule/_files/create_some_data_here.php

and not somewhere like this:
app/code/MyNamespace/MyModule/Test/....../_files/create_some_data_here.php

Can @magentoDataFixture files be inside the module itself and not on default directory dev/tests/integration/testsuite?

magento2 testing phpunit integration-test

share|improve this question

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657

/**
 * @magentoDataFixture MyNamespace/MyModule/_files/create_some_data_here.php
 */
class CustomIntegrationTestTest extends AbstractController
{

share|improve this question

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657

share|improve this question

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657

asked Jun 4 at 11:38

Matheus GontijoMatheus Gontijo

1657