From c292fbc46dc71ad1e36b7f9b4b11fce3894b57e4 Mon Sep 17 00:00:00 2001
From: FireFly <firefly@firefly.nu>
Date: Sat, 5 Apr 2025 17:11:17 +0200
Subject: [PATCH] tests: actually test printing of paths in unit test

This seems to be a copypasta mistake that slipped through when writing the
initial tests.  Changes the ValuePrintingTests::tPath to actually test a path
value instead of a string.

Change-Id: I20fe72635a0b1a6a0d72f674a4619da0de9f3d44
---
 tests/unit/libexpr/value/print.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/unit/libexpr/value/print.cc b/tests/unit/libexpr/value/print.cc
index b03b164b7..0e777c8d0 100644
--- a/tests/unit/libexpr/value/print.cc
+++ b/tests/unit/libexpr/value/print.cc
@@ -42,8 +42,8 @@ TEST_F(ValuePrintingTests, tString)
 TEST_F(ValuePrintingTests, tPath)
 {
     Value vPath;
-    vPath.mkString("/foo");
-    test(vPath, "\"/foo\"");
+    vPath.mkPath("/foo");
+    test(vPath, "/foo");
 }
 
 TEST_F(ValuePrintingTests, tNull)