Andrey/uptime-kuma
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: add type field to condition test objects

Browse Source 
The processMonitorConditions function expects conditions with
type: 'expression' field. Fixed test cases to use correct format.
This commit is contained in:
mkdev11 2026-01-06 03:57:34 +02:00
parent 8b145d2522
commit 11f451d7f2
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
test/backend-test/monitors/test-mqtt.js
View File

@ -164,6 +164,7 @@ describe("MqttMonitorType", {
test("check() sets status to UP when message condition matches (contains)", async () => {
const conditions = JSON.stringify([
{
type: "expression",
variable: "message",
operator: "contains",
value: "KEYWORD"
@ -177,6 +178,7 @@ describe("MqttMonitorType", {
test("check() sets status to UP when topic condition matches (equals)", async () => {
const conditions = JSON.stringify([
{
type: "expression",
variable: "topic",
operator: "equals",
value: "sensors/temp"
@ -189,6 +191,7 @@ describe("MqttMonitorType", {
test("check() rejects when message condition does not match", async () => {
const conditions = JSON.stringify([
{
type: "expression",
variable: "message",
operator: "contains",
value: "EXPECTED"
@ -203,11 +206,13 @@ describe("MqttMonitorType", {
test("check() sets status to UP with multiple conditions (AND)", async () => {
const conditions = JSON.stringify([
{
type: "expression",
variable: "topic",
operator: "equals",
value: "test"
},
{
type: "expression",
variable: "message",
operator: "contains",
value: "success",