App Stress Test

Planning on collecting a TON of data???

I'm talking tens of thousands of records

We can take your app and generate 100k records of mock data, and push your app to the breaking point.

Find out just how good your app-design holds up

You think you've designed the perfect system? Let's put it to the test! (^_^)

Seriously though, after you've spent what seems like hundreds of hours pouring over the AppSheet documentation, and investing dozens of hours building out your app; after you've gone through all that trouble, the only way to see how bad things can get... is to wait and see!?

Not in my vocabulary

Thankfully, there are services out there (like Mockaroo) that you can use to generate mock data; and if you learn their systems good enough, you can do all sorts of crazy dependent-relationship things and generate hierarchical data. (^_^)

How It Works

Grant Access

Generate Mock Data

App Testing

Generate Report

The first thing that needs to happen is the granting of access to whichever app's data source you're wanting to test. This allows us to get the names of your columns, as well as allowing us to put the mock data into your system during testing.

Access and Edit Permissions to the AppSheet app will also need to be granted, this way we can review the performance profiler to assess where the problems lie.

The next step of the process is to take your tables, import them into a mock data generator and generate some data. This is the part that takes the longest, as we've got to set up and relational connections and ensure that sufficiently detailed data is generated.

The number of tables you have, as well as the complexity of the connections between them, determines the base cost of this service. (see table below)

Once the data is generated, it's then imported into your tables to see what effect it has on your app. Several different levels of data will be tested, each level tested 10 times:

100% of the mock dataset
75% of the data
50% of the data
25% of the data

Care must be taken when testing for sync times; AppSheet has multiple layers of systems in place to help reduce sync time and increase performance of your app, so you must follow a specific protocol in order to avoid things that could skew the data (cache of data on the device, for instance).

From all those syncs, a report will be generated that gives a breakdown of how you can expect your app to perform as data is collected over time.

This report includes things like:

Average sync time at each level (as well as max & min)
Breakdown of sync-type difference between different roles (if you have them)
Identification of where the delays are coming from
Brief comments on what could be done to increase efficiency
Overall summary of what you can expect as time progresses

To view a sample of what the report looks like, click here

Report
Sample

Get Yours Today

Complete the form below to begin the process

Base Cost

{# of tables} against {Complexity} = Base Cost

The base cost of this service is a function of the number of tables you have, against the complexity between them.

"Basic" apps, with few reference connections between the tables, are relatively straight-forwards to generate data for - even if there's a high number of tables.

"Intermediate" apps, which feature reference connections between the tables heavily, are harder to generate data for (because of the increased complexity).

"Professional" apps, one's built using traditional data modeling principles - with several reference hierarchies, multiple layers inside the hierarchies, and a bunch of supporting tables - are much more time consuming to generate mock data for.

Number	Title	Currency Code	Total	Invoice	Issue Date	Valid Through Date	Acceptance Date	Source	Source Ref ID