[Scummvm-devel] Game testings

Sat Jun 18 20:58:35 CEST 2016

Thanks for the feedback and giving it a thorough run through.

I'll clean it up and fix those bugs. If you like I can throw this up on
github as well.

If I do that, it'll likely be MIT licensed, but it can be something else if
you prefer.

On Sat, Jun 18, 2016, 10:18 AM Eugene Sandulenko <sev.mail at gmail.com> wrote:

> Not bad for a start.
>
>
>    - The calendar item at the release creating is behaving weird, it was
>    not obvious on the date format, and I got "date cannot be blank", while the
>    data was there.
>    - Release numbers in the log are shown as object references.
>    - Unexpected requirement to provide comments at the game testing.
>    - No way to specify date of the test, except "now".
>    - Would be convenient to be able to jump to the entry right from the
>    log.
>    - List of releases would be nice to have the release in our
>    conventional format, e.g. 1.8.0 instead of the current 3 columns.
>    - Would be nice to list log for each user in their profile, as well as
>    overall statistics "10 tests".
>    - Need a conventional, preferably table-driven way of mass-adding
>    supported games associated with single release.
>    - Games may have several releases on several platforms, so we need
>    another level of hierarchy there.
>
> In general, I like it.
>
>
> Eugene
>
>
> On 16 June 2016 at 05:15, Alex Bevilacqua <alex at alexbevi.com> wrote:
>
>> Hey guys. Been a couple of weeks so I thought I'd share the progress I'd
>> made on the game testing/management front.
>>
>> First, feel free to have a look at https://scummvm-gamesdb.herokuapp.com.
>> You'll need to create an account, but it's just email/username/password.
>> There's no mailer or anything and it's just to track interaction.
>>
>> I want to kick this off with what my goals were here as that might help
>> with feedback.
>>
>> I wanted to build a system to:
>>
>> * track communication around testing
>> * act as a games database
>> * act as a release database
>>
>> As it stands, there are a LOT of games that ScummVM supports, and I
>> personally feel that managing the communication surrounding releases and
>> testing has outgrown the basic wiki+forum approach.
>>
>> *Welcome Page*
>>
>> The system starts with a reverse-chronological activity stream that can
>> be used to show what's been happening within the system. I've only defined
>> events for when tests are created or versions/games are added, but we can
>> add additional events as needed.
>> [image: Inline images 1]
>>
>> *User Management*
>>
>> I didn't really build this out, though I added user impersonation. You'll
>> need to "sign up" a new user in order to create them, but once created, you
>> can impersonate and interact with the system. I added this to facilitate
>> testing and creating content.
>>
>> There's no ACL in the system at the moment, so everyone has the same
>> level of access. This will need to be locked down at some point.
>>
>> *Release Management*
>>
>> This section is for configuring when a release was made, what the version
>> information is and optionally a place to store (markdown formatted) release
>> notes.
>>
>> [image: Inline images 2]
>> I included this so that we can link games and game versions to specific
>> releases.
>>
>> *Platforms and Languages*
>>
>> I seeded the database with the platforms and languages used for building
>> detection entries.
>>
>> *Games*
>>
>>
>> *[image: Inline images 3]*
>>
>> Basic searching (by name) has been added, and the games list includes
>> some information about the game itself, when it was introduced to ScummVM
>> and when it was last tested.f
>>
>> If you drill down into a game, you can manage the versions of that game
>> that are supported, as well as the tests themselves.
>>
>> [image: Inline images 4]
>> I've defined a "version" as a release of the game that can be found in
>> the detection tables for a game. This can be used as a test target if a
>> user wants to specify *which* version of a game they were playing, or if
>> they want to just link the test to the game itself they can.
>>
>> *Test Management*
>>
>> This is kind of the main reason I started doing this.
>>
>> [image: Inline images 5]
>>
>> The tests are meant to capture information about the user's experience
>> while playing through a game using a specific version of ScummVM. This
>> information can then be rolled up to the game level to determine how long
>> it's been since a game was play-tested, as well as what version it was last
>> tested against.
>>
>> The fields that we're tracking can also be validated/enforced to help
>> ensure users are providing the most relevant test details, or to guide them
>> in the right direction.
>>
>> I've probably sunk about 6-8 hours into this now, but I'm still enjoying
>> it and am happy to continue. I wanted to submit this now though to start
>> getting some feedback as to whether this is a direction you'd be interested
>> in going.
>>
>> The application is hosted on heroku, with the database in postgres. I'll
>> setup a dockerfile for this as well to make local testing a lot easier for
>> people unfamiliar with Rails.
>>
>> This is still in pretty rough shape, but I think there's enough there to
>> form an initial proof-of-concept.
>>
>> Cheers ;)
>>
>> Alex
>>
>>
>> On 29 May 2016 at 21:16, Alex Bevilacqua <alex at alexbevi.com> wrote:
>>
>>> I put a few hours into it last week. I don't plan on getting more than a
>>> proof of concept written. It would suck to build this out just to  have it
>>> rejected, so I want to make sure you guys are good with it sooner rather
>>> than later.
>>>
>>> I'll keep plugging away at it though ;)
>>>
>>> On Sun, May 29, 2016, 7:52 PM Thierry Crozat <criezy at scummvm.org> wrote:
>>>
>>>> Hi Alex,
>>>>
>>>> We will still need to have some discussion in the team on whether we
>>>> want to accept it and how to maintain it.
>>>> But I am glad to see you are excited about this and am looking forward
>>>> to see what you can come up with.
>>>>
>>>> Thierry
>>>>
>>>> On 24 May 2016, at 18:45, Alex Bevilacqua <alex at alexbevi.com> wrote:
>>>>
>>>> Up to you guys if that's a big enough hurdle that we just shouldn't
>>>> proceed.
>>>>
>>>> I don't think it would be hard to get community support if necessary,
>>>> especially if this is all open source.
>>>>
>>>> I'll still get rolling on this since I'm excited about it, but if the
>>>> team wants this shelved, we can.
>>>>
>>>> On Tue, May 24, 2016, 1:37 PM Filippos Karapetis <bluegr at gmail.com>
>>>> wrote:
>>>>
>>>>> That might be an issue... we do not have a Ruby developer, and we'll
>>>>> need to set up a Ruby environment on our server, too (phusion passenger
>>>>> etc).
>>>>>
>>>>>
>>>>> On Tue, May 24, 2016 at 7:15 PM, Alex Bevilacqua <alex at alexbevi.com>
>>>>> wrote:
>>>>>
>>>>>> Ruby for sure ;)
>>>>>>
>>>>>> On Tue, May 24, 2016, 12:13 PM Filippos Karapetis <bluegr at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Sounds cool, but will you write it in PHP, or Ruby? (I'm asking
>>>>>>> cause I know you are a Ruby dev).
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> On Tue, May 24, 2016 at 2:57 PM, Alex Bevilacqua <alex at alexbevi.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Ok cool. I'll see what i can get done tonight and tomorrow night
>>>>>>>> and throw it up on Heroku for you guys.
>>>>>>>>
>>>>>>>> I'm thinking of including the following initially:
>>>>>>>>
>>>>>>>> * basic user management and user roles (admin, maintainer, user)
>>>>>>>> * basic administration (manage scummvm version, create/manage games)
>>>>>>>> * allow game variations (language, platform, version)
>>>>>>>> * comments!
>>>>>>>> * activity stream (comments, updates/additions to platform ... etc)
>>>>>>>>
>>>>>>>> I figure that's ambitious enough for now, and if I can actually
>>>>>>>> deliver should give you a feel for what this could be (and if it would fit
>>>>>>>> into the scummvm online ecosystem)
>>>>>>>>
>>>>>>>> I'll post all the code to github as it takes shape.
>>>>>>>>
>>>>>>>> On 24 May 2016 at 07:49, Eugene Sandulenko <sev.mail at gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 24 May 2016 at 13:46, Alex Bevilacqua <alex at alexbevi.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Just out of curiosity, would you guys be interested in a custom
>>>>>>>>>> solution for managing the games catalogue and games compatibility?
>>>>>>>>>>
>>>>>>>>>> This is something I've wanted to write for a little while now.
>>>>>>>>>>
>>>>>>>>>> If you're interested, I can try to do a quick proof of concept. I
>>>>>>>>>> always envisioned a cross between the dosbox compatibility list and the
>>>>>>>>>> wine appdb.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Absolutely!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Eugene
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Mobile security can be enabling, not merely restricting. Employees
>>>>>>>> who
>>>>>>>> bring their own devices (BYOD) to work are irked by the imposition
>>>>>>>> of MDM
>>>>>>>> restrictions. Mobile Device Manager Plus allows you to control only
>>>>>>>> the
>>>>>>>> apps on BYO-devices by containerizing them, leaving personal data
>>>>>>>> untouched!
>>>>>>>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>>>>>>>> _______________________________________________
>>>>>>>> Scummvm-devel mailing list
>>>>>>>> Scummvm-devel at lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/scummvm-devel
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> "Experience is the name every one gives to their mistakes" - Oscar
>>>>>>> Wilde
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> "Experience is the name every one gives to their mistakes" - Oscar
>>>>> Wilde
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Mobile security can be enabling, not merely restricting. Employees who
>>>> bring their own devices (BYOD) to work are irked by the imposition of
>>>> MDM
>>>> restrictions. Mobile Device Manager Plus allows you to control only the
>>>> apps on BYO-devices by containerizing them, leaving personal data
>>>> untouched!
>>>>
>>>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________
>>>> Scummvm-devel mailing list
>>>> Scummvm-devel at lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/scummvm-devel
>>>>
>>>>
>>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160618/24fc86dd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 69603 bytes
Desc: not available
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160618/24fc86dd/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 44049 bytes
Desc: not available
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160618/24fc86dd/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 109842 bytes
Desc: not available
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160618/24fc86dd/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 63972 bytes
Desc: not available
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160618/24fc86dd/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 54820 bytes
Desc: not available
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160618/24fc86dd/attachment-0004.png>