Adventure Works sales
revenue was —, — on . Internet sales keep — of revenue as gross margin; reseller sales keep —.
Revenue by month
The selected year is in full color; click a month or a year label to switch years. Reseller orders are booked in monthly batches, so a few months have none.
Revenue by product category
Split by channel, on one scale. Margins below zero are in red.
Revenue by sales territory
Territory of the sale. Hover a row for the split by channel.
Top 15 product models
Ranked by revenue for the selected year and channel. Sizes and colors of a model are combined.
| # | Model | Revenue | Margin |
|---|
Reseller quota attainment
Quotas are set for reseller sales reps, so this card shows reseller sales whatever channel is picked. The tick marks the quota.
Revenue is the warehouse's sales amount, in US dollars. Gross margin is revenue minus standard product cost, as a share of revenue. Years are calendar years. The warehouse's partial months at either end (the last days of December 2010 and January 2014) are left out. Quota attainment compares each rep's reseller sales with their quota, over the quarters that have a quota. Data comes from the AdventureWorks data warehouse in your local Postgres database (adventureworks).
TestGen scores adventureworks at —. Its latest test run, on —, passed — of — tests on the adventureworks table group. Every one of the — tests on the columns the Sales page reads passed, so the open issues don't touch its figures.
Quality score breakdown
Open in TestGenTestGen multiplies the profiling score by the testing score. Below the formula, each impact dimension's score and the issues pulling it down.
Critical data elements alone score —.
Quality score over time
Each point is a TestGen scorecard refresh, which happens after every profiling and test run.
What TestGen tests
Open in TestGenNobody wrote these tests by hand. TestGen generated every one from its profile of the data and set each threshold from what it saw.TestGen generated most of these from its profile of the data; the rest were written or edited by hand.
By quality dimension
By test type
Tables behind the Sales page
Open in TestGenTests counted here are the ones on columns the Sales page reads, plus table-level tests. The table score and other open issues cover every column, including ones it doesn't use. Click a row to see the table's columns in the catalog.
| Table | Tests | Passed | Status | Table score |
|---|
Open test issues
Open in TestGenEvery test that failed or warned in the latest run. The same — have come up on every run since —. Click a row to see the table in the catalog.
| Status | Table | Column | Test | Rows flagged |
|---|
Test runs
Open in TestGenEach run of the adventureworks test suite. Schedule: —, — time.
| Run | Tests | Passed | Failed | Warnings | Score |
|---|
Monitors
Open in TestGenTestGen's freshness and volume monitors learn each table's normal pattern. They only log results until they have — runs of history, then start alerting.
No monitors are set up for this table group in TestGen yet.
Hygiene issues from profiling
Open in TestGenWhat TestGen's profiler flagged, grouped by how likely each is to be a real problem.
Results come from TestGen for the adventureworks table group: its test suite and monitors, and the table group's latest profiling run. A test "on a column the Sales page reads" is one whose column appears in its queries, or a table-level test on a table those queries use. In the live dashboard, every card, table, and column links back to the matching page in TestGen. Those links are turned off in this public copy.
TestGen watches all — adventureworks tables for freshness, volume and schema drift. In — runs, — tables changed row count and — columns changed in the schema. Every result is logged, not alerted, until the monitors have — runs of history.The monitors have enough history to alert.
No monitors yet
Open in TestGenTestGen isn't monitoring adventureworks yet. Turn on monitoring for the table group in TestGen, and this page will show each table's freshness, volume and schema drift once the first run finishes.
Table monitors
Open in TestGenEach line is the table's row count at every run since —; grey means it never moved. A table is late when it goes longer than TestGen expects without changing. While the monitors learn, that is logged, not alerted.
How the monitors are set up
Open in TestGenTestGen predicts each table's next freshness and volume from its own history, using these settings.
Monitor runs
Open in TestGenScheduled every — hours. A longer gap means a scheduled run didn't happen, which pushes back the date alerts can start.
| Run | Gap | Logged | Alerts |
|---|
Schema drift
Open in TestGenTestGen records every column it sees and logs any column added, dropped or retyped after that.
Results come from TestGen's monitor suite for adventureworks and its schema log. Times are shown in the monitor schedule's time zone. In the live dashboard, every card, table, and column links back to the matching page in TestGen. Those links are turned off in this public copy.
TestGen has profiled — tables and — columns in the adventureworks table group. It marks — columns as critical data elements and — as personal data. The Sales page reads — of them.
Semantic types TestGen found
From values alone, TestGen works out what each column holds, beyond its database type. Click a type to list its columns.
Personal data TestGen flagged
Columns TestGen's profiler marked as personally identifiable, by kind and risk. This dashboard never shows their values.
Tables
Open in TestGenClick a row to list the table's columns below. Click a header to sort.
Columns
Click a row to open the column's TestGen profile below. Semantic type is TestGen's reading of what a column holds; Failing counts tests that failed or warned in the latest run.
No columns match. Clear the search or pick another table.
Column profile
Open in TestGenWhat TestGen learned about one column when it profiled it, and every check it runs on it.
Catalog entries come from TestGen's data catalog for the adventureworks table group, as of its latest profiling run. Column scores combine profiling and testing results the same way the table and table-group scores do. In the live dashboard, every card, table, and column links back to the matching page in TestGen. Those links are turned off in this public copy.