Roscrea QA Application Guide for Skyrim SE Testing
Table of Contents
- Introduction
- QA Testing Overview
- Beta Comments & Bug Reporting
- Other Bugs and Reporting
- Application Instructions
---
Introduction
Ahoy there! Welcome to the first step to joining the BS: Roscrea's Quality Assurance Department.
Before we can let you in - we gotta know what you can bring to the table. To that end, our friends over at BS: Cyrodiil have developed an application test for QA, which we'd like you to undertake. Simply follow the instructions below, and we'll treat that as your application. Once we have had a chance to look at the results of your application, we'll send you an email.
The application process requires you to test a sample quest and dungeon, looking for the types of bugs/issues you might encounter during an actual QA test. QA testing is a very broad task. As you might know, Skyrim is a buggy game which results from it being a very large game where many systems interact with each other. You might encounter bad pathing, misplaced assets, lighting problems, subtitle errors and much more. Quests can be broken in many ways. Doing the quest in an order that the designer didn’t intend, using gameplay mechanics to break various parts of the quest or not behaving as the quest tells you to are common ways to find errors.
For submitting bugs that are specifically related to a certain placed object, we use a feature called beta comments. This mod is required to use it, make sure to install its dependencies too. To report a bug, you open the console and enter bc \"What is buggy about this\". When you close the game, you will find a file called betacomments.txt in your game folder. Be aware that this file will be emptied every time you start the game, so make sure to back it up.
For other or more complex bugs (i.e. in quests), we use bullet point lists to get a report that is as short as possible, but as detailed as it needs to be to understand the bug.
There are no right or wrong answers, and no minimum or maximum number of issues to spot; just let us know what you find! You should play through the dungeon/quest multiple times, as it has some branching options that result in different bugs.
Application Instructions
1. Download QATest.7z and set it up for testing in Skyrim SE.
2. Install Console Commands Extender, Fuz Ro D-oh and their dependencies. Only available on pre-AE for now, use this to downgrade.
3. You can start the quest at a new farmhouse nearby Western Watchtower (where you kill the first dragon). The quest will send you to the test dungeon in its plot.
4. Play through the quest and explore the dungeon. Use beta comments, create a bullet point list. Then fill in the Roscrea Application Form where you provide a link to a .zip file with your beta comments file(s) and your bullet point list as the work sample.
Good Luck!
QA Testing Overview
The application process requires you to test a sample quest and dungeon, looking for the types of bugs/issues you might encounter during an actual QA test. QA testing is a very broad task. As you might know, Skyrim is a buggy game which results from it being a very large game where many systems interact with each other. You might encounter bad pathing, misplaced assets, lighting problems, subtitle errors and much more. Quests can be broken in many ways. Doing the quest in an order that the designer didn’t intend, using gameplay mechanics to break various parts of the quest or not behaving as the quest tells you to are common ways to find errors.
There are no right or wrong answers, and no minimum or maximum number of issues to spot; just let us know what you find! You should play through the dungeon/quest multiple times, as it has some branching options that result in different bugs.
Beta Comments & Bug Reporting
For submitting bugs that are specifically related to a certain placed object, we use a feature called beta comments. This mod is required to use it, make sure to install its dependencies too. To report a bug, you open the console and enter bc \"What is buggy about this\". When you close the game, you will find a file called betacomments.txt in your game folder. Be aware that this file will be emptied every time you start the game, so make sure to back it up.
For other or more complex bugs (i.e. in quests), we use bullet point lists to get a report that is as short as possible, but as detailed as it needs to be to understand the bug.
There are no right or wrong answers, and no minimum or maximum number of issues to spot; just let us know what you find! You should play through the dungeon/quest multiple times, as it has some branching options that result in different bugs.
Other Bugs and Reporting
There are no right or wrong answers, and no minimum or maximum number of issues to spot; just let us know what you find! You should play through the dungeon/quest multiple times, as it has some branching options that result in different bugs.