Rayrun
← Back to Discord Forum

Test data maintenance in Typescript-playwright framework

pallavi9929posted in #help-playwright
Open in Discord
pallavi9929

What are the common ways everyone is maintaining automation test data ? (where same data can be used across DEV, QA and UAT). Any pros and cons to be mindfull of? while designing this? Is excel a good option or a Config file?

This thread is trying to answer question "What are the common ways everyone is maintaining automation test data that can be used across DEV, QA and UAT? Are there any pros and cons to be mindful of while designing this? Is excel a good option or a Config file?"

2 replies

Would think it all depends what is most convienent for you that fits your needs. A json file you read, use express to host an end point where your test make Rest calls for GET/POST... Or could be a test generated library and using a test data generator like Bogus or Faker. Which is better apples or lemons. Actually i much prefer sour food 😋. Nice thing with Faker/Bogus you cna seed the generator to get deterministic random data.

butchmayhew
butchmayhew

I talk about managing test data in this post https://playwrightsolutions.com/the-definitive-guide-to-api-testcreating-a-datafactory-to-manage-test-data/

I’ve been able to get by without storing any data in Json or excel files using this approach, even across multiple environments in my job.

TwitterGitHubLinkedIn
AboutQuestionsDiscord ForumBrowser ExtensionTagsQA Jobs

Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email luc@ray.run.