File Testing

[Knoobish]

Re: File Testing

Know what would be nice? If file senders without a file in the queue or in the game had to get at least 2 blue or red testers to test their file before they sent it in to help filter out the crap going into the queue. I'm sure some of it will still get rejected, but it would definitely help if we had enough people supporting it.

This could be verified by having the people who submit their files also submit a PM or something from the blue/red tester saying that X file(s) are good to go into the game.

[bluguerrilla]

Re: File Testing

That's a little bureaucratic but if someone were to manage it it could work out to save the FFR-Testers time.

Know what would be really neat? If instead of running this all through e-mail it could be run through part of the site.

That way a group of initial testers (such as R1 file authors, we're trusty people) could do a run through on files whenever they want and give feedback and other people could give authorization to move onto the batch. I dunno, just ideas.

[omgitznpv]

Re: File Testing

Know what would be nice? If file senders without a file in the queue or in the game had to get at least 2 blue or red testers to test their file before they sent it in to help filter out the crap going into the queue. I'm sure some of it will still get rejected, but it would definitely help if we had enough people supporting it.

This could be verified by having the people who submit their files also submit a PM or something from the blue/red tester saying that X file(s) are good to go into the game.

This would be terrific- people who never knew what they were doing could be forced to heed (well, at least note) others' advice. I see a few things with this suggestion, however.

Though blue/red testers have agreed to test all files sent their way (or try to, actually), this would create an overload of work for them. It's kind of like a pre-batch- these testers would become more of the judges (jx/rebirth/tass), so they have to judge all these files before going into the batch, which get judged before they get into the queue. We probably can't do this until we have a whole bunch of people willing to test files. If one tester has had enough work, they can simply inform someone (such as myself) to indicate in this thread not to send them any files (until the next batch?).

In addition, if we were to have numerous blue/red testers state x number of files should be noted in the batch, it would get confusing (overlapped x files and such). It would be better for the testers to say what files they judged going into the batch, and once a file is noted twice, then it becomes present in the batch.

How would random simartists be aware that they need to do so? You'd have to place this throughout every thread that gives directions, or inform everybody that sent an untested file that they must get it tested.

I think one blue/red tester for now would be enough, though two or more would still help. This would lessen the possible workload that I see.

Great suggestion; I'm sick of seeing a whole lot of crap in each batch (like what my first files were like, rofl) that just creates more and more work for Rebirth/jx/Tass. Also, this forces each stepartist to have to spend more and more time on each file to perfect it, lessening their output even further. This could result in batch notes coming sooner.

Know what would be really neat? If instead of running this all through e-mail it could be run through part of the site.

That way a group of initial testers (such as R1 file authors, we're trusty people) could do a run through on files whenever they want and give feedback and other people could give authorization to move onto the batch. I dunno, just ideas.

This would definitely help the quality and quantity of files that go in each batch, which I'm sure everybody would prefer. But like I said, this is like a pre-batch batch and that seems like a little too much, especially with the fact that our output going into each batch has been drastically cut.

[Knoobish]

Re: File Testing

That's a little bureaucratic but if someone were to manage it it could work out to save the FFR-Testers time.

Know what would be really neat? If instead of running this all through e-mail it could be run through part of the site.

That way a group of initial testers (such as R1 file authors, we're trusty people) could do a run through on files whenever they want and give feedback and other people could give authorization to move onto the batch. I dunno, just ideas.

I was thinking this as well. It would be a lot more convenient to have a forum to run that through.

This would be terrific- people who never knew what they were doing could be forced to heed (well, at least note) others' advice. I see a few things with this suggestion, however.

Though blue/red testers have agreed to test all files sent their way (or try to, actually), this would create an overload of work for them. It's kind of like a pre-batch- these testers would become more of the judges (jx/rebirth/tass), so they have to judge all these files before going into the batch, which get judged before they get into the queue. We probably can't do this until we have a whole bunch of people willing to test files. If one tester has had enough work, they can simply inform someone (such as myself) to indicate in this thread not to send them any files (until the next batch?).

In addition, if we were to have numerous blue/red testers state x number of files should be noted in the batch, it would get confusing (overlapped x files and such). It would be better for the testers to say what files they judged going into the batch, and once a file is noted twice, then it becomes present in the batch.

How would random simartists be aware that they need to do so? You'd have to place this throughout every thread that gives directions, or inform everybody that sent an untested file that they must get it tested.

I think one blue/red tester for now would be enough, though two or more would still help. This would lessen the possible workload that I see.

Great suggestion; I'm sick of seeing a whole lot of crap in each batch (like what my first files were like, rofl) that just creates more and more work for Rebirth/jx/Tass. Also, this forces each stepartist to have to spend more and more time on each file to perfect it, lessening their output even further. This could result in batch notes coming sooner.

Well, getting the word out wouldn't be a big problem. A forum announcement would be enough to get the word out, and if they can't figure out to look at a help forum before sending in a file for the first time, it's prolly gonna be crap anyways unless they are a pretty good SM simfile artist or something.

I was thinking as long as one person says yeah, the file is good, it's good to go for the batch.

We'd only have to get 4-5 people doing this as a prejudge: there's not THAT many new simfile artists, and they'll still have to stick to the 2 file rule. The only potential problem I see is these people getting lazy, and then it just slows up the process even more. So the blue/red testers would have to be pretty active about the process.

It was just a thought. As long as we're setting up this thread, I figured this may be a good idea.

This would definitely help the quality and quantity of files that go in each batch, which I'm sure everybody would prefer. But like I said, this is like a pre-batch batch and that seems like a little too much, especially with the fact that our output going into each batch has been drastically cut.

The batches are still pretty large. And its not even like it's all experience simfile artists sending in 5 files each, it's still a LOT of new people.

[omgitznpv]

Re: File Testing

I was thinking this as well. It would be a lot more convenient to have a forum to run that through.



Well, getting the word out wouldn't be a big problem. A forum announcement would be enough to get the word out, and if they can't figure out to look at a help forum before sending in a file for the first time, it's prolly gonna be crap anyways unless they are a pretty good SM simfile artist or something.

I was thinking as long as one person says yeah, the file is good, it's good to go for the batch.

We'd only have to get 4-5 people doing this as a prejudge: there's not THAT many new simfile artists, and they'll still have to stick to the 2 file rule. The only potential problem I see is these people getting lazy, and then it just slows up the process even more. So the blue/red testers would have to be pretty active about the process.

It was just a thought. As long as we're setting up this thread, I figured this may be a good idea.

Forgot about announcements. lole.

If this is implemented, it should be a process like this:

Simartist submits to tester -> tester gives feedback -> tester imforms (Tass?) -> simartist edits or whatever -> submits

If (Tass?) doesn't get imformed, I guess he can tell the simartist they need a tested file.

I'm still trying to think of with a better way to do this, if there is.

[chidori!]

Re: File Testing

can i be a tester pleeesssssseeeeee with 2 tacos and a pizza on top
sonictailsshadow@msn.com

[omgitznpv]

Re: File Testing

can i be a tester pleeesssssseeeeee with 2 tacos and a pizza on top
sonictailsshadow@msn.com

Any experience? You know, you need to state o_o

Listing you as a black tester until you say you're otherwise.

[chidori!]

Re: File Testing

can i be a tester pleeesssssseeeeee with 2 tacos and a pizza on top
sonictailsshadow@msn.com

Any experience? You know, you need to state o_o

Listing you as a black tester until you say you're otherwise.

not relly.. i make my own simfiles but i dont submit them

[omgitznpv]

Re: File Testing

I'll test files, but only for the people who have a good chunk of knowledge already.

E-mail? People need to know where to send their files to.

I'll make note of that, however.

[dandandamdandan1111]

Re: File Testing

I could be a tester if you want. dandandamdandan1111@flashflashrevolution.com
I had submitted or four files last batch and three of them got a +?.

[bluguerrilla]

Re: File Testing

If this is implemented, it should be a process like this:

Simartist submits to tester -> tester gives feedback -> tester imforms (Tass?) -> simartist edits or whatever -> submits

That's entirely too much legwork. If anything like this happened it would have to rely on much less communication. I don't know whether Tass actually cares to know whether a file gets tested.

If this did happen it would probably be better just to do a rough filter of the sims so that offsync POS files never make it to the batch. I'm not sure how much time that would actually save the testers though.

[omgitznpv]

Re: File Testing

tass talk

[shad0wlord]

Re: File Testing

I'll test files I suppose.

shad0wlord@live.com

I'd label myself as a green tester. I make files, but none of which have been queue'd.

[[TeRa]]

Re: File Testing

i can test stuff.

[unkdavar]

Re: File Testing

I'll test files. unkdavar@gmail.com