We're changing our architecture currently, it's documented through links on
here :
https://wiki.mozilla.org/Gaia/New-Architecture-Program

I can't speak much on anything else but Software Quality.
We have various levels of automation testing that's documented here :
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing

We also do manual exploratory/session-based testing on new features/bugs
that land to verify and find new bugs.  This finds a good number of our
bugs faster than running through a regression test suite manually.  It also
reduces the cost of maintenance work on areas for automation if a feature
is still evolving.  In order to help map out exploratory testing, sometimes
we create state diagrams based on ui/blackbox or what UX calls IA (
http://www.wikiwand.com/en/Information_architecture ). Sometimes instead we
create a matrix of what needs to be tested, etc.  I personally prefer to
test in a MVC model manner so that we isolate if it's a data, function or
view issue.

We have our automation to do manual regression checking and we have manual
testers who also double check in case we miss something in our manual
testing.  We are in the process of ramping up our automation.

One of the interesting other projects not mentioned in automation is the
image compare automation.
it's in jenkins for arabic/french/italian for the settings app.  This will
be expanded later.

We are also exploring the idea with property base testing: (
http://www.scalatest.org/user_guide/property_based_testing )

In terms of metrics: there's an automation for performance and also a mean
time between failure.   Currently we do not have any code coverage tool
that will help us out over all.  Adding more tests does not necessarily
mean more coverage.  We need a way to verify the code is covered correctly
to help verify the validity of the automated tests.  I believe this is also
being investigated.


On Wed, Nov 18, 2015 at 1:28 AM, Samuel Alonso <[email protected]> wrote:

> Hello
>
> I am currently doing a Master in Computer Engineering in A Coruña. I am
> writing this email because I have to make an important project for the
> master, and as I am so keen on Firefox OS, then I will focus my job on
> Gaia. One of the most important step is to make a interview to the project
> developers so that they can discuss things about it, so my job would be
> better and I would learn more about it. Some of the issues, I would like to
> know and I find important for my project, are:
>
>
> - Software Architecture : patterns, diagrams UML
>
> - Software Design : design patterns and anti-patterns
>
> - Software Quality : metrics , testing
>
> - Accessibility
>
> - Methodology
>
> Kind regards, Samuel
>
> _______________________________________________
> dev-fxos mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-fxos
>
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to