How Do You QA Test a Tsundere Android!?

Test 30: Anomalia Server

"Just make them lift it, heh."

Eric shrugs while chuckling.

"Yeah... that's one way to go about it."

I murmur as I recall the first time I tried to raise Lily from the bed, naively following Eric's instructions.

With "How to reproduce" finished, the "Expected behaviour" and "Actual behaviour" sections are easy to fill in.

Expected: Light as a feather.

Actual: Heavy as a tank.

Of course, both are phrased more elegantly and businesslike on the form.

Next, I hover over the "Product" dropdown box to choose the specific product for which this bug is relevant. It will be fairly challenging to find Lily's model among all of Anomalia's products... or so I thought.

As soon as I click on the box, it opens only three suggestions: "Tsundere-Chan Model", "Tsundere-Chan Remote" and "Tsundere-Chan Pod". There's also a serial code beside each name, but I ignore those.

Eric briefly explains that the system filters out Anomalia products which are irrelevant for me. Makes sense, I shouldn't have the option to report bugs on products which I haven't even seen.

The remaining obligatory fields are "Severity" and "Priority".

"I trust you know what they mean."

"Yeah, though I also know that their precise definition changes depending on the workplace."

At least, that's what I discovered while googling QA related subjects for job interviews. With that in mind, I tell him how my previous job used to treat these important fields.

"Severity was a way to gauge how critical the bug is to the general functioning of the product, whereas Priority stated how important it was to fix the bug in the immediate future."

Down to it: Severity was overshadowed by Priority most of the time. The developers prioritized fixing whatever the higher ups set as the highest priority, even if these bugs weren't fatal to the product in term of functionality.

"It's the same here. Submit based on that line of reasoning."

Eric nods in approval to my explanation.

"Should I submit the Priority as well? Shouldn't someone from above decide something like that?"

"Yes, in most cases the higher ups will have the final saying. Treat your submissions as 'advice' on that front."

In term of Severity, the design flaw of Lily's weight doesn't hinder the system much. Being super heavy doesn't cause software crashes, freezes, data loss or anything critical.

Therefore, I report it as Severity 4. This is the highest numeric value for the field, which makes it the LEAST severe possible.

As for Priority, I slap it a proper Priority 1 - a "critical" priority.

While Lily's weight doesn't cause technical errors in her functions, it's bound to disappoint and challenge many consumers. Thus, it has a critical importance in term of business value.

Once done, the final logical step should be assigning the bug to some developer. After all, someone gotta fix it.

Yet, I can't find such a field anywhere.

"Don't I need to assign it to someone?"

"Do you have any idea to whom this should be directed?"

"Not really..."

"Me neither."

Eric shrugs with a carefree smile.

"Then I just leave the bug hanging in the air?"

"Don't worry about that part, it'd work itself out."

"If you say so..."

Still shrouded in doubt, I hover over the "Submit" button and turn to Eric. He nods in approval and I hit the button.

After a short loading - the submission form disappears. A small message appears at the bottom of the screen: "Successfully Submitted."

"Here you can see the bugs related to you."

Eric points at the left side of the screen.

"The current status of the bug is here."

He points at the word "Queued".

"Queued...? For what?"

"Everything you submit will pass by the Sweeper, right now it's queued for being examined."

"Sweeper...?"

"Oh, right. I forgot that this is unique to Anomalia."

He scratches his head with an awkward smile. As always, he's good at forgetting the important details.

"The company is big and the products are complicated, so Anomalia decided to use its capabilities to craft a sorting AI - the Sweeper. It goes over every task and bug submitted into the server and analyzes them."

This is rather revolutionary; I don't think such technology exists anywhere else in the present.

"The Sweeper finds the right person to assign the bug to, without the submitter lifting a finger. It also knows how to spot duplicates of the same bug and to reject them. "

This explains why Eric wasn't worried about opening a bug which definitely already exists. The system will just sweep it away as a duplicate!

... wait, does that mean all the effort I put into this report was be for naught? Eric! You troll!!

"When a bug is fixed and closed, the Sweeper converts it into a task and sends it to the relevant QA department for testing."

If it works as well as he describes it, this technology saves lots of trouble for both QA and developers.

"Now you pretty much know everything you need, the rest is up to you."

Eric jumps on his feet and starts heading toward the exit. I also stand up and follow him outside.

"I'll be very busy for the rest of the day, it's likely we'll only meet again next week."

"Oh, right..."

It's already Friday, which means weekend is just around the corner.

"For today, try submitting some bugs to the server, see how the Sweeper responds."

"Is there anything specific you'd like me to test?"

"I'm already drowning in confirmed bugs and I have to release a new build version today. I'd rather not add more trouble to my plate."

"Heh, got it."

We part ways and Eric heads to his office. I step back into the office and use my card to close the door behind me.

He confirmed that he'll be too busy to pay me another visit today. Which means... I can safely bring out the Lego for Lily!

-------------------------------------------------------------

／人◕ ‿‿ ◕人＼ Don't forget to vote if you liked the chapter!