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.

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

Bulk data for testing orgs with large amounts of data #3

Open
acrosman opened this issue Oct 17, 2019 · 2 comments
Open

Bulk data for testing orgs with large amounts of data #3

acrosman opened this issue Oct 17, 2019 · 2 comments
Labels
documentation Improvements or additions to documentation Ready for Sprint Can easily be worked on during an SFDO Sprint use case

Comments

@acrosman
Copy link
Contributor

Orgs expected to have large amounts of data, need to have fairly large data sets for testing. The details of the data do not matter a great deal, but do need the volume to ensure triggers, flow, and similar, have appropriate filters.

As a developer I want to generate data sets large enough to use most, or all, of the storage in a partial or full sandbox to QA build with large volumes.

@allisonletts
Copy link
Contributor

This functionality may be handled, at least in part, with Paul's internal code for LDV generation. Our primary use case for the data generation tool is a midsize dataset generation--large enough that the dataset can cover interesting permutations, but not true LDV.

@acrosman acrosman added documentation Improvements or additions to documentation Ready for Sprint Can easily be worked on during an SFDO Sprint labels Sep 23, 2020
@acrosman
Copy link
Contributor Author

Snowfakery, and some other tools, can do this well right now, but lack examples and documentation to make it easy even for an expert to generate the data.

Likely this issue can be split into multiple issues one for each tool that we end up creating docs/samples for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Ready for Sprint Can easily be worked on during an SFDO Sprint use case
Projects
None yet
Development

No branches or pull requests

2 participants