# QA Tests

{% hint style="info" %}
This page contains background information for MariaDB developers.
{% endhint %}

### Optimizer and the Random Query Generator <a href="#optimizer-and-the-random-query-generator" id="optimizer-and-the-random-query-generator"></a>

The RQG[^1] is used to test various Optimizer features. See [Optimizer Quality](/docs/server/reference/product-development/server-development/quality/optimizer-quality.md) for more information.

### Aria Engine Recovery <a href="#aria-engine-recovery" id="aria-engine-recovery"></a>

The [QA - Aria Recovery](/docs/server/reference/product-development/server-development/quality/qa-aria-recovery.md) page contains a plan on how to test it.

### Upgrade and Installer Testing <a href="#upgrade-and-installer-testing" id="upgrade-and-installer-testing"></a>

* Upgrades using `.deb` and RPM packages are tested using very simple tests in BuildBot by the various `bld_kvm*` builders.

#### TODO <a href="#todo" id="todo"></a>

* More complex tests around `.deb`, RPM and tarballs.
* Decide on specific upgrade/downgrade paths (e.g. MySQL 5.5 to MariaDB 2.2?) and methods (`mysqldump`, `mysql_upgrade`) that we support and test each individually.
* Test the Windows installer and service NSIS allows for scripted unattended installs by providing an `/SD` argument to functions such as `MessageBox`.
* Test the contents of the Windows package, e.g. if `HELP`, `.test`, and other files are properly placed and runnable.

### Linking Testing <a href="#linking-testing" id="linking-testing"></a>

The purpose of those tests is to check that various applications that use `libmysql` can be compiled, linked and run with MariaDB. They are run by the `compile-connectors` builder in BuildBot.

* Perl `DBD::mysql`
  * We configure and compile the Perl DBI MySQL driver. Then we run the test suite provided with it.
* PHP
  * We configure and compile both the `mysql` and `mysqli` PHP drivers without `mysql-nd`. For each, we run those tests from the PHP test suite that are known to be good (other tests fail for both MySQL and MariaDB).
* TODO: Perl and PHP with the embedded library.

### Connectors Testing <a href="#connectors-testing" id="connectors-testing"></a>

The purpose of those tests is to check that the libraries that implement the MySQL protocol can work with MariaDB.

* The `libmysql` library/connector is tested both by the MTR test suite (since `mysqltest` links with it).

#### TODO <a href="#todo" id="todo"></a>

* PHP with the `mysql-nd` driver
* Connector C++
* JDBC

### Replication Testing <a href="#replication-testing" id="replication-testing"></a>

Individual applications:

* group commit:

  ```perl
  perl runall.pl \
    --engine=InnoDB \
    --grammar=conf/replication/rpl_transactions.yy \
    --gendata=conf/replication/rpl_transactions.zz \
    --mysqld=--sync_binlog=1 \
    --mysqld=--innodb-flush_log_at_trx_commit=1 \
    --mysqld=--binlog-dbug_fsync_sleep=100000 \
    --mysqld=--default-storage-engine=InnoDB \
    --threads=15 \
    --queries=1M \
    --duration=600 \
    --validator=None 
  ```

[^1]: Random Query Generator


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mariadb.com/docs/server/reference/product-development/server-development/quality/qa-tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.