test(bug): issue with tibiaNewslist and tibiaNews inside TestFakeToUpCodeCoverage

[tobiasehlert]

Both following tests are failing with 502 instead of an 200.

tibiaNewslist:

tibiadata-api-go/src/webserver_test.go

Lines 176 to 187 in 6f1a6d6

	w = httptest.NewRecorder()
	c, _ = gin.CreateTestContext(w)
	c.Params = []gin.Param{
	{
	Key: "days",
	Value: "90",
	},
	}
	tibiaNewslist(c)
	assert.Equal(http.StatusOK, w.Code)

tibiaNews:

tibiadata-api-go/src/webserver_test.go

Lines 189 to 200 in 6f1a6d6

	w = httptest.NewRecorder()
	c, _ = gin.CreateTestContext(w)
	c.Params = []gin.Param{
	{
	Key: "news_id",
	Value: "6607",
	},
	}
	tibiaNews(c)
	assert.Equal(http.StatusOK, w.Code)

Currently:
Those two test-cases in TestFakeToUpCodeCoverage are commented out for now by #511.

[hiSandog]

These tests should not depend on the live Tibia news upstream if their purpose is webserver coverage; a recorded/fake response for both list and detail endpoints would make 200 behavior deterministic and reserve 502 for a separate upstream-failure case. It is worth checking whether the two paths share a changed fixture URL or parser assumption, since both failing together suggests one dependency rather than two handlers. Re-enabling them with an explicit success fixture plus malformed/upstream-error fixtures would improve coverage without restoring flakiness.