test(tracker-core): clarify db compatibility test usage

Author: josecelano

packages/http-protocol/src/v1/responses/scrape.rs

@@ -133,7 +133,7 @@ mod tests {
         }
 
         #[test]
-        fn should_saturate_large_download_counts() {
+        fn should_encode_large_download_counts_as_i64() {
             let info_hash = InfoHash::from_bytes(&[0x69; 20]);
             let mut scrape_data = ScrapeData::empty();
             scrape_data.add_file(

packages/tracker-core/src/databases/driver/mysql.rs

@@ -355,7 +355,8 @@ mod tests {
 
     Test for this driver are executed with:
 
-    `TORRUST_TRACKER_CORE_RUN_MYSQL_DRIVER_TEST=true cargo test`
+    `TORRUST_TRACKER_CORE_RUN_MYSQL_DRIVER_TEST=true \
+     cargo test -p bittorrent-tracker-core --features db-compatibility-tests run_mysql_driver_tests`
 
     The `Database` trait is very simple and we only have one driver that needs
     a container. In the future we might want to use different approaches like:
@@ -456,6 +457,8 @@ mod tests {
         driver
     }
 
+    // This test is invoked by `.github/workflows/testing.yaml` in the
+    // `database-compatibility` job to validate supported MySQL versions.
     #[tokio::test]
     async fn run_mysql_driver_tests() -> Result<(), Box<dyn std::error::Error + 'static>> {
         if std::env::var("TORRUST_TRACKER_CORE_RUN_MYSQL_DRIVER_TEST").is_err() {