GemaGomez

Differences between revisions 1 and 2
Revision 1 as of 2012-12-11 14:25:55
Size: 612
Editor: 188-221-246-203
Comment:
Revision 2 as of 2012-12-17 13:40:03
Size: 2980
Editor: 188-221-246-203
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.3em;"><<TableOfContents>>||

== Contact Information ==


|| Name || Gema Gomez-Solano||
|| IRC || gema ||
|| Find me in: || freenode - #ubuntu-quality||
|| Launchpad || https://launchpad.net/~gema.gomez ||
&nbsp;
Line 10: Line 19:
Describe yourself here I like to tinker with software and it normally breaks before I realise. I used to be a developer back in the day, but I broke more code around my components than creating great software, so a colleague back then suggested that maybe I would be more suited for QA. He was right.

I started breaking software for a living doing security audits, which are mainly manual testing, and then moved on to do test automation for a living. I like to write test cases that are future proof, and I like to report test results in a way that they are useful for developers to be able to fix the problems.

I am as worried about development&testing processes as I am worried about the testing itself, because good testing is normally at the heart of any good development&testing process.

Doing test automation for Ubuntu has opened my mind to new challenges, such as how to do collaborative automated testing. The complexity of trying to test a product as dynamic as Ubuntu has taught me a lot about testing and test automation, and I am learning more every day about Ubuntu.

I have strong opinions when it comes to testing. One of my most controversial themes seems to be: ''"No testing is better than bad testing."''
Line 13: Line 30:
== Contact Information ==

|| IRC || gema ||
|| Launchpad || https://launchpad.net/~gema.gomez ||
Line 20: Line 33:
Write your contributions here.
 * Active member of the [[https://wiki.ubuntu.com/QATeam/|QA Team]].
 * I have been trying to gather as much information about test automation as possible on the [[https://wiki.ubuntu.com/QATeam/AutomatedTesting|Automated testing wiki]].


=== Main projects ===
Led technically:

 * [[https://launchpad.net/utah|Ubuntu Automation Test Harness]]
 * [[https://launchpad.net/qa-dashboard|QA Dashboard]]

And we are working on structuring the automation of the Platform QA team and the contributions from the community around the following projects:
 * [[https://launchpad.net/ubuntu-test-runlists|Platform QA runlists:]] or the tests that run in the lab.
 * [[https://launchpad.net/ubuntu-test-cases| Test cases repositories:]] test cases maintained by test cases developers, all these test cases can be run in the lab in all sorts of different configurations.

=== Reporting ===

 * [[http://reports.qa.ubuntu.com/|QA dashboard]] in production.


 
Line 24: Line 57:
Write your goals here. I'd like to continue to improve the automation for Ubuntu. I'd like to help others to come up with good test cases and help them add them to the pool we already have.

Contact Information

Name

Gema Gomez-Solano

IRC

gema

Find me in:

freenode - #ubuntu-quality

Launchpad

https://launchpad.net/~gema.gomez

 

About Me

I like to tinker with software and it normally breaks before I realise. I used to be a developer back in the day, but I broke more code around my components than creating great software, so a colleague back then suggested that maybe I would be more suited for QA. He was right.

I started breaking software for a living doing security audits, which are mainly manual testing, and then moved on to do test automation for a living. I like to write test cases that are future proof, and I like to report test results in a way that they are useful for developers to be able to fix the problems.

I am as worried about development&testing processes as I am worried about the testing itself, because good testing is normally at the heart of any good development&testing process.

Doing test automation for Ubuntu has opened my mind to new challenges, such as how to do collaborative automated testing. The complexity of trying to test a product as dynamic as Ubuntu has taught me a lot about testing and test automation, and I am learning more every day about Ubuntu.

I have strong opinions when it comes to testing. One of my most controversial themes seems to be: "No testing is better than bad testing."

Contributions

Main projects

Led technically:

And we are working on structuring the automation of the Platform QA team and the contributions from the community around the following projects:

Reporting

Future Goals

I'd like to continue to improve the automation for Ubuntu. I'd like to help others to come up with good test cases and help them add them to the pool we already have.

Testimonials

If you know me and have something nice to say, please leave a comment here.

GemaGomez (last edited 2016-11-30 12:39:16 by localhost)