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

Test data integration #55

Open
ruettenm opened this issue Apr 24, 2020 · 1 comment
Open

Test data integration #55

ruettenm opened this issue Apr 24, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@ruettenm
Copy link
Collaborator

It would be great to add a new menu entry to switch into some "testdata" mode. So it's easy to take screenshots without any production gopass store.

One solution could be:

  • Load the renderer app with a query parameter like ?test-data=1 when the "test-data"-mode is active.
  • In the app we could simple check for this query param with the following snipped and always return some static list of secrets.
const url = new URL(document.location.href)
const SHOW_TEST_DATA = url.searchParams.has('test-data')
@ruettenm ruettenm added the enhancement New feature or request label Apr 24, 2020
@jonas-pietzsch
Copy link
Contributor

The thing I don't like about this: if you want to do a full demo about the tool, including modification the Gopass store (add, delete, edit secret values etc) a simple test data provider is not enough.

After adding or deleting a secret Gopass UI retrieves all secret names again and re-builds the navigation tree. When using hard-coded test data, one would need to implement a mocked version of Gopass that behaves like real Gopass in terms of deletion, adding, editing and so on. I don't have a good feeling about adding this to the production code. Also it's more work.
I would prefer having a shell script that generates a Gopass store with test data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants