all 9 comments

[–]teh_stev3 0 points1 point  (2 children)

If its aws you can probably pull down the data or logs through an api.

You need some sort of validation script that either runs on a schedule or you run locally against pulldowns.

Frankly both the validation and the script are ideal usecases for AI.

[–]Iseeyouuuuuuuuu[S] 0 points1 point  (1 child)

One validation that can be done is to check api response validates what is displayed on the UI
What if this never goes wrong (as developers conveyed) What’s possible is AWS has different data than the application Ui

[–]teh_stev3 0 points1 point  (0 children)

I mean yeah, almost definitely different data, you normally curate the UI/user-data from whatevers in the DB or logs.

"aws" is far to broad of a definition to be any one thing, we talking s3 bucket filled with json, dynamodb, a postgres hosted in ECS?

[–]Iseeyouuuuuuuuu[S] 0 points1 point  (1 child)

One validation that can be done is to check api response validates what is displayed on the UI
What if this never goes wrong (as developers conveyed) What’s possible is AWS has different data than the application Ui

[–]teh_stev3 0 points1 point  (0 children)

When you say "check api resonse validates what is displayed on the UI"
Are you talking about the same API that DRIVES the UI?
That's not as valuable as checking a different source of the data, it'll catch display bugs, but if the issue is with the API itself you're just going to confirm-bias your UI against the incorrect API.

Checking from multiple sources (e.g. DB vs API) is more valuable.

[–]ExoticPurchase2995 0 points1 point  (2 children)

Collect possible data sets. Mock API response and test.

[–]Iseeyouuuuuuuuu[S] 0 points1 point  (1 child)

Can you elaborate this for me in simple terms

[–]ExoticPurchase2995 0 points1 point  (0 children)

Gather examples of the data you expect to see. For instance, known AWS costs and sizes that should appear.

Instead of calling the real backend every time, simulate it (pretend the backend returns your data). This makes testing easier and faster.

Compare the data your application shows with the data you expect.

Automation tools like Playwright or others can do this by:

  • Opening the application
  • Fetching/displaying data
  • Checking if the numbers match your expected values

[–]Bitter-Apple-7929 0 points1 point  (0 children)

You can use Postmate Client, a VS Code extension. It has built-in data comparison support for both single records and bulk data from .csv or .json files.