STEP:Mod Testing: Difference between revisions
From Step Mods | Change The Game
TechAngel85 (talk | contribs) |
TechAngel85 (talk | contribs) |
||
Line 190: | Line 190: | ||
==External Mod Testing Procedure== | ==External Mod Testing Procedure== | ||
=====Step 1 - Opening Post/Workflow===== | =====Step 1 - Opening Post/Workflow===== | ||
Read the mod's | Read the mod's topic opening post (OP). | ||
: | :Here, an outline of what needs to be tested for the particular mod can be found. Make note of this and use it when in-game testing begins. If nothing is outlined in the OP, take steps to establish an outline for testing. This outline should include what options should be tested, how to test, steps to take to make the mod compatible with other mods in STEP, etc. | ||
=====Step 2 - Nexus Page===== | =====Step 2 - Nexus Page===== | ||
Read the Nexus Page in | Read the Nexus Page in its entirety | ||
:Read the mod's Nexus page description completely as well as the changelog (if provided). Make note of any special installation/uninstall instructions, | :Read the mod's Nexus page description completely, as well as, the changelog (if provided). Make note of any special installation/uninstall instructions, any known issues with the mod or mod compatibility issues, and of any potential conflicts with the DLCs and/or other STEP mods. The changelog can often provide a sense of where the author is taking the mod and what might be expected from a mod and its author in the future. Add relevant information to the mod topic OP. | ||
=====Step 3 - Mod's Comments===== | |||
=====Step 3 - Mod's | Read the Nexus comments | ||
Read the Nexus | :A complete read is not necessary; however, try to develop a sense of user satisfaction and a list of possible bugs to attempt to confirm or deny (bugs can also be listed in the page's Bug tab when provided). This is also a good way to find out how active the author is with the mod. No replies from the author in a long period of time usually indicates they have been absent or may no longer be actively supporting the mod. | ||
:A complete read is not necessary; however, try to develop a sense of user satisfaction and a list of possible bugs to attempt to confirm or deny. This is also a good way to find out how active the author is with the mod. No replies from the author in a long period of time usually indicates they have been absent or may no longer be actively supporting the mod. | |||
=====Step 4 - Documentation===== | =====Step 4 - Documentation===== | ||
Examine the documentation included with the mod | Examine the documentation included with the mod | ||
:Read the Readme and any other documentation which comes with the mod. Note any lack of clarity, installation/uninstall directions, and general completeness. If the mod does not include documentation, please make note of this as well for the final review and mod page creation. | :Read the Readme and any other documentation which comes with the mod. Note any lack of clarity, installation/uninstall directions, and general completeness. If the mod does not include documentation, please make note of this as well for the final review and mod page creation. | ||
=====Step 5 - Validation===== | =====Step 5 - Validation===== | ||
Validate the archive package, naming scheme, and directory structure using your mod manager or 7zip. | Validate the archive package, naming scheme, and directory structure using your mod manager or 7zip. | ||
: Observe if the downloaded mod package is properly structured and configured for installation | : Observe if the downloaded mod package is properly structured and configured for installation or not. Mod Organizer can also use BAIN type installations; however, FOMODs are preferred which use XML. You can validate the FOMOD XML using an online validation tool. W3Schools has an always up-to-date [http://www.w3schools.com/xml/xml_validator.asp XML Validator]. | ||
=====Step 6 - DDSopt===== | =====Step 6 - DDSopt===== | ||
Use DDSopt to determine quality of texture compression for texture mods. | Use DDSopt to determine quality of texture compression for texture mods, when needed. | ||
: The [http://wiki.step-project.com/Guide:DDSopt DDSopt Guide] can help; however, basic knowledge of texture compression and familiarity with DDSopt will be required. | : The [http://wiki.step-project.com/Guide:DDSopt DDSopt Guide] can help; however, basic knowledge of texture compression and familiarity with DDSopt will be required. | ||
=====Step 7 - TES5Edit===== | =====Step 7 - TES5Edit===== | ||
Inspect the mod in TES5Edit to determine quality of edits of any plugin files and the scope of mod | Inspect the mod in TES5Edit to determine quality of edits of any plugin files and the scope of mod | ||
: Note any issues of the mod not carrying over changes from the DLCs and/or from the Unofficial Patches. Also note any conflicts with mods already in STEP. Knowledge of TES5Edit and conflict resolution will be required for this step. | : Note any issues of the mod not carrying over changes from the DLCs and/or from the Unofficial Patches. Also note any conflicts with mods already in STEP. Knowledge of TES5Edit and conflict resolution will be required for this step. Add relevant information to the mod topic OP. | ||
=====Step 8 - Installation/Uninstall===== | =====Step 8 - Installation/Uninstall===== | ||
* Validate the installation procedure | * Validate the installation procedure listed on the Nexus page. | ||
* Validate the uninstallation procedure | * Validate the uninstallation procedure listed on the Nexus page. | ||
=====Step 9 - Inspection===== | =====Step 9 - Inspection===== | ||
<ol> | <ol> | ||
<li> Inspect in MO<br/> | <li> Inspect in MO<br/> | ||
: | : Using Mod Organizer, take note of any conflicts that appear against vanilla Skyrim files and other STEP mods. Users should be familiar how to do this in MO. MO provides the option to extract BSAs during installation of the mod; however, with recent innovations in MO this is no longer necessary. Extracting BSAs should only be done when the need arises for conflict resolution.</li> | ||
<li> Run | <li> Run LOOT<br/> | ||
: Unless the mod is new on the scene, | : Unless the mod is new on the scene, LOOT will recognize it and provide some valuable information about the mod such as if the mod is clean or dirty, requires other mods, etc. Include this information, if any, in reviews.</li> | ||
</ol> | </ol> | ||
= In Game Testing Procedures = | = In Game Testing Procedures = |
Revision as of 17:42, July 5, 2016
Template:Warning Template:Notice Mod Testing for S.T.E.P. -- by the S.T.E.P. Team
- Updated: 17:42:46 5 July 2016 (UTC)