Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Please add a test database in a later dev release - suggestion. #451

Closed
chrom opened this issue Dec 25, 2013 · 3 comments
Closed

Please add a test database in a later dev release - suggestion. #451

chrom opened this issue Dec 25, 2013 · 3 comments
Labels
improvement

Comments

@chrom
Copy link
Contributor

chrom commented Dec 25, 2013

This simplifies the testing, and enables fast look for a certain functionality.
Probably it is necessary put separately SQL dump.
@verklov
Copy link
Contributor

verklov commented Dec 25, 2013

Hello chrom,
You apparently mean some sample data, right? So far there is no valid sample data that we can provide and we cannot promise it will be ready by the later dev release. We certainly have this on our plans, but have not set the date yet.

@chrom
Copy link
Contributor Author

chrom commented Dec 26, 2013

I believe that this decision will help the community to find errors faster.

@verklov
Copy link
Contributor

verklov commented Dec 26, 2013

Agree, having some sample data makes life a bit easier :)
We will most likely have it in one of the future releases, but please do not expect it too soon.

@verklov verklov closed this as completed Dec 26, 2013
vpelipenko added a commit that referenced this issue Jul 15, 2015
@vpelipenko
Merge pull request #451 from magento-qmt/develop
1ea9173 
[Mavericks] Move all test data to repositories
okorshenko pushed a commit that referenced this issue Dec 14, 2016
Merge pull request #451 from magento-okapis/okapis-2.1.3-pr
90045f0 
Fixed issues:
 - MAGETWO-56928: CLONE - Wrong algorithm for calculation batch size on category indexing
 - MAGETWO-57001: [Backport] - Admin user with access to only one website is unable to edit a product - for 2.1
 - MAGETWO-58742: [Backport] After upgrading from 2.0.7 to 2.1, editing a category gives a 500 error - for 2.1.3
@AleksLi AleksLi mentioned this issue Feb 17, 2018
Merged
fe-lix- pushed a commit to fe-lix-/magento2 that referenced this issue Apr 6, 2018
@AleksLi
magento#451 disabled sources tab content on manage_stock update
48082ba
fe-lix- pushed a commit to fe-lix-/magento2 that referenced this issue Apr 6, 2018
@AleksLi
magento#451 disabled sources tab content on manage_stock update
8ebfef0
fe-lix- pushed a commit to fe-lix-/magento2 that referenced this issue Apr 6, 2018
Merge pull request magento#559 from magento-engcom/451_assigned_sourc…
70ba0ea 
…es_disabled

 magento#451 disabled sources tab content on manage_stock update
magento-engcom-team added a commit that referenced this issue Mar 13, 2019
@magento-engcom-team
ENGCOM-4486: 419 test coverage get available payment methods customer #…
93f57b9 
…451

 - Merge Pull Request magento/graphql-ce#451 from magento/graphql-ce:419-test-coverage-getAvailablePaymentMethods-customer
 - Merged commits:
   1. 44e24e3
   2. 8786fbf
   3. 1356caa
   4. b8006ee
   5. 31166c9
magento-engcom-team pushed a commit that referenced this issue Mar 13, 2019
@naydav
ENGCOM-4486: 419 test coverage get available payment methods customer #…
8718692 
…451
magento-devops-reposync-svc pushed a commit that referenced this issue May 24, 2022
@slopukhov
Merge pull request #451 from magento-performance/CABPI-395
87b74b1 
CABPI-395: Fix Failed Magento Health Index Tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrom @verklov