Welcome to Testers Incorporated! A new and better way of acquiring testers for your hack!
IF YOU ARE HERE FOR MUNDANE PRAISE AND NOT CONSTRUCTIVE CRITICISM, OR YOU WANT TO TEST A HACK JUST AS A SNEAK PREVIEW, THEN PLEASE: SHOW YOURSELF OUT OF THIS THREAD.
This will not be tolerated anymore. See Introduction and Rules.
1. Introduction and Rules
2. Types of Testers
3. Apply to be a Tester
4. Hire a Tester
5. List of Testers
1. Introduction and Rules
As most of you know, we used to have a "Testers for Hire" thread; a rather old, unorganized, deprecated, and slightly non-serious thread where hack creators can hire testers to give feedback on their hacks. Due to the oldness of the thread, it has been closed.
This thread will revive the testers for hire idea, only in a much more organized, serious, and definitely regularly updated way. I will not copy the old list from the old Testers for Hire thread; we will start fresh. There will also be a "trust" system. Testers with a "star"
next to their name have a good reputation of giving helpful feedback. See (Hire a Tester)
You might be thinking what I mean by "more serious", well, it will be clear in these new following set of rules:
RULES
Testers:
1. You must follow the application form and post it in this thread. (See "Types of Testers" and "Apply to be a Tester")
2. You must give proper, constructive (helpful), feedback and criticism. Testers who expect the job of testing as some sort of "fun, sneak preview" and only give "IT WAS GOOD KEEP UP THE GOOD WORK" feedback are not tolerated. Creators have the right to tell me (through PM) if their tester did or did not do their work. Though, I may need some sort of evidence (e.g a snap shot or a file of what feedback they gave). (See Hire a Tester)
3. Testers inactive for 2 months will be deleted. They may come back when they want to. Though, if this becomes a regular thing, you will not be allowed back.
4. Your "transaction" with your Hirer will happen through PM. Do not post your feedback in this thread.
Hirers/Creators:
1. I reserve you the right to give feedback to me about testers.
2. Do not overwhelm testers.
3. Make sure you read the testers' "description" before hiring them. (See Hire a Tester)
4. Having your hack tested does not mean your giving away sneak previews of your uber awesome hack, and does not mean you should expect mundane praise to increase your ego. A tester's purpose is to criticize and scrutinize. Expect constructive feedback about your hack, and some may come off harsh.
5. I suggest you at least hire two testers.
6. Complaining to me about a tester and how he "hurt your feelings" with his feedback is not valid.
7. Your transaction with your tester will happen through PM. Do not post it in this thread. (See Hire a Tester)
Rules will be updated as we go on.
^Back to Top^
2. Types of Testers
There are two categories of testers in this thread, but there are three types of it.
Bug Testers:
Bug testers look for glitches. They are expected to scrutinize even the most mundane of objects to find possible bugs. Creators usually should do their best to fix these glitches, especially fatal ones. Aesthetics is another aspect of glitches. Bug testers go hand in hand with Play Testers.
Tasks:
~~~~
Play Testers:
Play testers look for level design issues. They are expected to scrutinize level design, from aesthetics to game play. Creators should prioritize fixing level design. Play testers go hand in hand with Bug Testers.
Tasks:
~~~~
Proofreaders:
Proofreaders focus on grammar in text boxes, and other places like the Title Screen and some art in-levels. They are expected to scrutinize grammar and spelling, so check message boxes carefully. Proofreaders should also take aesthetics in - meaning, what kind of alignment looks right? Creators should make sure they are telling the proofreader where to look for mistakes. Doing this will avoid making the proofreader strangle for all possible text.
Tasks:
NOTE: Don't forget about the Castle Cutscene!
~~~~
Kaizo Testers:
Tools are allowed.
Tasks:
^Back to Top^
3. Apply to be a Tester
YOU MUST FOLLOW THE APPLICATION BELOW TO APPLY AS A TESTER
Quick Link to Application
I will explain. Your application is you resume or portfolio of sorts. In the list, instead of linking to your profile, I will link to your post. This post will contain a description of what kind of tester you are, and other things. This will also make my life easier by CTRL+F-ing the Key word "Profile".
Application
^Back to Top^
4. Hire a Tester
Creators should hire a tester either by posting here, or through a PM. Asking for a tester here will open the request up to everyone, though it may get drowned. Through a PM, you will be able to contact your favored tester while avoiding one you don't want.
There is a new "trust", or reputation system. Creators/Hirers have the right to give feedback to me about their certain tester (through PM). If I get enough "positives" about a tester, I will put a "star" next to there name to show if they are a good tester. Hirers, as I've said in the rules, shouldn't not complain about constructive criticism. I will ask for evidence for both positive and negative feedback.
The members linked in the list are actually links to their application forms, which contains a description and overview of what kind of tester they are. I suggest Hirers read those if they are choosing to PM a tester instead of posting here.
I strongly recommend that hack creators hire Bug/Play Testers and Proofreaders before releasing their hack. This is to polish your hack.
^Back to Top^
5. List of Testers
^Back to Top^
IF YOU ARE HERE FOR MUNDANE PRAISE AND NOT CONSTRUCTIVE CRITICISM, OR YOU WANT TO TEST A HACK JUST AS A SNEAK PREVIEW, THEN PLEASE: SHOW YOURSELF OUT OF THIS THREAD.
This will not be tolerated anymore. See Introduction and Rules.
1. Introduction and Rules
2. Types of Testers
3. Apply to be a Tester
4. Hire a Tester
5. List of Testers
1. Introduction and Rules
As most of you know, we used to have a "Testers for Hire" thread; a rather old, unorganized, deprecated, and slightly non-serious thread where hack creators can hire testers to give feedback on their hacks. Due to the oldness of the thread, it has been closed.
This thread will revive the testers for hire idea, only in a much more organized, serious, and definitely regularly updated way. I will not copy the old list from the old Testers for Hire thread; we will start fresh. There will also be a "trust" system. Testers with a "star"
next to their name have a good reputation of giving helpful feedback. See (Hire a Tester)You might be thinking what I mean by "more serious", well, it will be clear in these new following set of rules:
RULES
Testers:
1. You must follow the application form and post it in this thread. (See "Types of Testers" and "Apply to be a Tester")
2. You must give proper, constructive (helpful), feedback and criticism. Testers who expect the job of testing as some sort of "fun, sneak preview" and only give "IT WAS GOOD KEEP UP THE GOOD WORK" feedback are not tolerated. Creators have the right to tell me (through PM) if their tester did or did not do their work. Though, I may need some sort of evidence (e.g a snap shot or a file of what feedback they gave). (See Hire a Tester)
3. Testers inactive for 2 months will be deleted. They may come back when they want to. Though, if this becomes a regular thing, you will not be allowed back.
4. Your "transaction" with your Hirer will happen through PM. Do not post your feedback in this thread.
Hirers/Creators:
1. I reserve you the right to give feedback to me about testers.
2. Do not overwhelm testers.
3. Make sure you read the testers' "description" before hiring them. (See Hire a Tester)
4. Having your hack tested does not mean your giving away sneak previews of your uber awesome hack, and does not mean you should expect mundane praise to increase your ego. A tester's purpose is to criticize and scrutinize. Expect constructive feedback about your hack, and some may come off harsh.
5. I suggest you at least hire two testers.
6. Complaining to me about a tester and how he "hurt your feelings" with his feedback is not valid.
7. Your transaction with your tester will happen through PM. Do not post it in this thread. (See Hire a Tester)
Rules will be updated as we go on.
^Back to Top^
2. Types of Testers
There are two categories of testers in this thread, but there are three types of it.
Bug Testers:
Bug testers look for glitches. They are expected to scrutinize even the most mundane of objects to find possible bugs. Creators usually should do their best to fix these glitches, especially fatal ones. Aesthetics is another aspect of glitches. Bug testers go hand in hand with Play Testers.
Tasks:
- Test every level as all possible forms of Mario, and if allowed, Yoshi and its variations.
- Explain exactly how you found/got the glitch.
- Screenshots of the glitch help. If it was unexpected and is hard to recreate, just explain how it happened.
- Fatal glitches are the most important bugs to be found; keep an eye more for things that could possibly kill the player or the game.
~~~~
Play Testers:
Play testers look for level design issues. They are expected to scrutinize level design, from aesthetics to game play. Creators should prioritize fixing level design. Play testers go hand in hand with Bug Testers.
Tasks:
- Test every level as all forms of Mario, and if allowed, Yoshi and its variations.
- Never test using tools. Unless the level calls for it. (Then, that's a sure sign of bad level design.
- Try not beating around the bush, but it helps if you don't just drop your feedback on someone and tell them it's God's word; your task is to help them, not to harass them.
~~~~
Proofreaders:
Proofreaders focus on grammar in text boxes, and other places like the Title Screen and some art in-levels. They are expected to scrutinize grammar and spelling, so check message boxes carefully. Proofreaders should also take aesthetics in - meaning, what kind of alignment looks right? Creators should make sure they are telling the proofreader where to look for mistakes. Doing this will avoid making the proofreader strangle for all possible text.
Tasks:
- Look for grammar and spelling errors.
- Keep alignment in mind
NOTE: Don't forget about the Castle Cutscene!
~~~~
Kaizo Testers:
Originally posted by Ultimaximus
I would say Kaizo hacks are typically tested for:
Variety/Creativity: To use techniques or tricks that require the player to respond in different ways, particularly, different than what was required of the player earlier in the level or in other hacks. Repeating tricks that you've already used or copying something from other hacks is frowned upon
Difficulty: That the hack is actually difficult and thus would be considered "Kaizo". Too difficult, where you require slowdown, wall-jumps, etc. and your hack gets considered a "pit" hack (named after Moltov's Pit of Death and Pit of Despair). You also want to avoid artificial difficulty, which is a bit hard to define actually in the case of Kaizo hacks..
Breaks: It is common in Kaizo hacks for players to be able to "break" a level, in which obstacles are skipped or mitigated due to an oversight of the creator, or a glitch that the player can do. Thus, creators and players work to find and prevent these breaks.
Extra: Plot, graphics, and music are generally considered extra bonus fluff that nobody requires of Kaizo hacks. Custom code such as gameplay elements or sprites could be used for new level ideas and techniques, but are not necessary for people to enjoy a Kaizo hack.
Variety/Creativity: To use techniques or tricks that require the player to respond in different ways, particularly, different than what was required of the player earlier in the level or in other hacks. Repeating tricks that you've already used or copying something from other hacks is frowned upon
Difficulty: That the hack is actually difficult and thus would be considered "Kaizo". Too difficult, where you require slowdown, wall-jumps, etc. and your hack gets considered a "pit" hack (named after Moltov's Pit of Death and Pit of Despair). You also want to avoid artificial difficulty, which is a bit hard to define actually in the case of Kaizo hacks..
Breaks: It is common in Kaizo hacks for players to be able to "break" a level, in which obstacles are skipped or mitigated due to an oversight of the creator, or a glitch that the player can do. Thus, creators and players work to find and prevent these breaks.
Extra: Plot, graphics, and music are generally considered extra bonus fluff that nobody requires of Kaizo hacks. Custom code such as gameplay elements or sprites could be used for new level ideas and techniques, but are not necessary for people to enjoy a Kaizo hack.
Tools are allowed.
Tasks:
- Keep sane.
- Look for creativity.
- Aesthetics are also key.
^Back to Top^
3. Apply to be a Tester
YOU MUST FOLLOW THE APPLICATION BELOW TO APPLY AS A TESTER
Quick Link to Application
I will explain. Your application is you resume or portfolio of sorts. In the list, instead of linking to your profile, I will link to your post. This post will contain a description of what kind of tester you are, and other things. This will also make my life easier by CTRL+F-ing the Key word "Profile".
Quote
Profile
Currently Testing: Hack(s) you are Currently Testing
Type of Tester: Three categories: Bug and Play Tester; Proofreader, and Kaizo Testers
Max. Amount of Levels/Worlds: Amount of levels/worlds you will test at a time
Description:
A short description of whatever.
Currently Testing: Hack(s) you are Currently Testing
Type of Tester: Three categories: Bug and Play Tester; Proofreader, and Kaizo Testers
Max. Amount of Levels/Worlds: Amount of levels/worlds you will test at a time
Description:
A short description of whatever.
Originally posted by Sample
Profile
Currently Testing: Hack Mario World
Type of Tester: Bug and Play Tester; Proofreader
Max. Amount of Levels/Worlds: 15 Levels; 2 Worlds
Description:
I am better at proofreading than bug and play testing. The most I will test as a bug and play tester are 10-15 levels a set, or 2 worlds.
Currently Testing: Hack Mario World
Type of Tester: Bug and Play Tester; Proofreader
Max. Amount of Levels/Worlds: 15 Levels; 2 Worlds
Description:
I am better at proofreading than bug and play testing. The most I will test as a bug and play tester are 10-15 levels a set, or 2 worlds.
Application
[b]Profile[/b]
[b]Currently Testing:[/b]
[b]Type of Tester:[/b]
[b]Max. Amount of Levels/Worlds:[/b]
[b]Description:[/b]
[b]Currently Testing:[/b]
[b]Type of Tester:[/b]
[b]Max. Amount of Levels/Worlds:[/b]
[b]Description:[/b]
^Back to Top^
4. Hire a Tester
Creators should hire a tester either by posting here, or through a PM. Asking for a tester here will open the request up to everyone, though it may get drowned. Through a PM, you will be able to contact your favored tester while avoiding one you don't want.
There is a new "trust", or reputation system. Creators/Hirers have the right to give feedback to me about their certain tester (through PM). If I get enough "positives" about a tester, I will put a "star"
next to there name to show if they are a good tester. Hirers, as I've said in the rules, shouldn't not complain about constructive criticism. I will ask for evidence for both positive and negative feedback.The members linked in the list are actually links to their application forms, which contains a description and overview of what kind of tester they are. I suggest Hirers read those if they are choosing to PM a tester instead of posting here.
I strongly recommend that hack creators hire Bug/Play Testers and Proofreaders before releasing their hack. This is to polish your hack.
^Back to Top^
5. List of Testers
^Back to Top^
Youtube Channel!
