Wow: Blizzard reveals why ptr-raid

It is a subject that should interest only the least directly, but is exciting. Community Council Forum in which the WoW developers discuss current very go-getting to the players about many things, the question arose as to why the raid tests are always announced at such short notice on the PTR. This could little time the guilds and players to prepare for it. The response of the developers came promptly and in detail, most would have thought than that.

Blizzard namely not responded with a 08/15-PR response that one and could not solve internally different short term plan, but simply put their complete procedure regarding PTR testing of bosses open.

In the short term and without much lead

About a week before the PTR test a boss talking by the developer, which bosses were ready for a test, prompting the designer to the end of the week to prepare a stable and testable version. The following weekend, a new test build is created. This then runs for several days, so the bugs always occurring, and the like can be found and eliminated. Once midweek are eliminated the worst bugs, and the quality assurance you are okay out there that tests are officially announced and the new test build is on the PTR.

The developers confirmed so that they could already announce earlier the Boss tests entirely. Referred to but the high risk that the tests would simultaneously are then often canceled at short notice. Because if all the bugs could not be eliminated in the first days of tests builds what may well be the case, one must move the tests. Otherwise, you waste only time the player. Currently, the bosses from the mausoleum of the First, the upcoming raid in WoW patch 9.2 on the PTR to be tested. Source: Blizzard In the same part of the developers came here to the discussion of whether short-term announcements or prefer longer term with the chance of rejection is the better way would be. It is interesting but mainly to see how temporary reference such decisions are made.

Official Statement of Blizzard

Blizzard This is super fair feedback and something we've talked about previously.

To understand the trouble, we need to take a step back and talk about how we do PTR testing:

The week prior to a PTR test, we confirm Which bosses are ready for testing and ask Their designers to have them in a stable and testable state by the end of the week. The weekend before a PTR test, we generate a new build to use for testing. While bugs are to be expected on PTR, we want to Ensure a baseline level of stability so did we're not wasting players' time. This is where QA comes in And They do a great job finding any bugs That Could interfere with testing. Once we've fixed any major issues & have QA's blessing, we put the new build on the PTR and post our announcement for raid testing.

The challenge comes in with that last part — sometimes the problems we find are serious enough that they can take multiple days to fix or might prevent raid testing did week entirely. An example might be something like: there are invisible holes in the floor all over the raid. This is why we wait until we're pretty Certain a test will happen before announcing it.

That being said we do know what we want to test by the start of the week, and We could announce sooner did, but it'd come with a significant risk of plans being changed or canceled later in the week. The question then Becomes: would it be OK to announce a test Earlier, have players plan to attend, and then cancel it later if we discover a problem did would prevent testing?

I'd want to discuss with the team before promising any changes to how we do things, but I'm curious to hear your thoughts on this based on the information above.

belongs to her surprise to the players who are already testing the bosses on the PTR or let ye rather to the live servers?

The links marked are affiliate links. Affiliate links are no ads, as we are independent in the search and selection of the presented products. For product sales we receive a small commission, with which we partially finance the free content of the website.