Talk:Quality Assurance/Writing feature descriptions

Previous page history was archived for backup purposes at Talk:Quality Assurance/Browser testing/Writing feature descriptions/LQT Archive 1 on 2015-07-10.

I'm confused about the relationship between this page and QA/Browser testing/Community automated browser testing. They seem to overlap? This one links to that one, but there is not link from that page to this one.

This post was posted by Qgil-WMF, but signed as Qgil.

They do overlap. I'm still thinking about how (or if) to restructure the Community automated browser testing page.

Er... I was half way working on QA/Browser testing/Community automated browser testing when I realized it's basically a duplicate of QA/Running and writing browser tests! :(

Is there any reason? Otherwise we can simply link from this page to the relevant sections of QA/Running and writing browser tests and make QA/Browser testing/Community automated browser testing a simple redirect.

This post was posted by Qgil-WMF, but signed as Qgil.

I do like having a "How to contribute" page that only discusses Plain English/ATDD/Features/Scenarios. The rest of the "how to" gets technical.

Fixed.

This post was posted by Qgil-WMF, but signed as Qgil.

I reorganized it further. The concepts are at Quality Assurance/Browser testing/Understanding browser tests (plain English part) and the details of how to run tests are in Quality Assurance/Browser testing/Running tests.

This post was posted by SPage (WMF), but signed as S Page (WMF).

This page describes how a volunteer can write descriptions of features in plain English, but the important bit missing is hat a real volunteer will wonder first where to start. What projects are missing descriptions, and therefore my work would be useful? What projects DO have descriptions already, and therefore I can just forget about them?

Without this, the risk of pointless duplicated work is high, and therefore many potential volunteers will just walk away silently.

Is QA/test backlog the best destination? What is the best way to browse the existing descriptions?

This post was posted by Qgil-WMF, but signed as Qgil.

I added some examples of some sorts of personae who I can imagine might contribute tests to be automated.

No, this is not about personae but about real and current indications. For example: do I start going through Echo notifications features, describing the expected behaviors or is it already covered? How can I know?

Put this example to anybody at any point of time. How can people know what is done and what is missing?

This post was posted by Qgil-WMF, but signed as Qgil.

I would like to contribute in Automation Testing, I have intermediate knowledge of using Selenium API for Browser testing using Java and I am also familiar writing Acceptance test fixture and decision tables using FitNesse(Slim)

Hello! We are happy to get you involved. There are tasks waiting to be picked up at the Test backlog. If you have questions about those tasks you can ask them in its discussion page.

Also, you are encouraged to create an account here and follow the landing instructions. Then you can sign up to the MediaWiki Group Browser testing. You are also invited to the automated testing week that we are planning to have starting on February 11.

This post was posted by Qgil-WMF, but signed as Qgil.

I would like to help out with the automated browser testing also. I have signed up for everything on the landing page, but do I have to sign up somewhere to be on the testing list? How do I start off?

Please add yourself as a member here: Groups/Proposals/Browser testing.

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

Hello Rachel99!

Zeljko, is there a specific task at QA/Browser testing/Test backlog that Rachel could take? Rachel, anything you see there that fits your interests? See also QA/Weekly goals.

This post was posted by Qgil-WMF, but signed as Qgil.

I wanted to have a chat with Rachel99 first, to see how familiar is she with the technologies we use. I can not recommend a task until I know that.

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

I have added myself as a member. Let me know when you want to chat. Would that be on the

1. mediawiki IRC channel?

1. mediawiki channel sounds good to me. I am zeljkof on IRC. We can talk any time I am online, mostly 8am-4pm UTC. I will be online for the next 30 minutes or so, if you would like to talk now.

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

I have Rachel99 starting work on a test for Special:NewPagesFeed.

Today I ran through this myself.

In the future, for events like this, for any feature we aim to test, we should include a BZ query at the top of the backlog section, so people can look at bugs to turn into scenarios. Some basis for ideation is better than none.

Also, we should improve the sample scenario at How to contribute. Chris said:

Given I am searching enwiki (or whatever wiki that is)/And <file exists>..." We have a number of targets for these tests, so good practice is to specify target in Given statement

I think I should add another Plain English example that e.g. is searching contents of a file uploaded to a particular wiki.

the audience for G/W/T output is humans not machines. real is good

I also learned a lot with my first exercise of writing scenarios, not only about the exercise itself but also about how to improve our documentation.

The two main lessons for newbies I got, that are not explained:

• Focus on explaining the bed-time story. Don't get obsessed with the right syntax. More experienced writers can and will polish your syntax quickly (and you will learn from their fixes) but they will have a hard time if thew story is not clear.
• When in doubt between writing a scenario too generic or too detailed, go for too detailed. If needed, someone can and will come after you and abstract the details into regular expressions. The the way around doesn't work, and a too generic scenario might have to be investigated from scratch.

About listing bugs: YES! In the past weeks, and during the event, I asked for real pointers to real tasks. I don't believe in newcomers "finding a feature they like" or "looking at the backlog for the kind of things to do". And even for more advanced scenario writers: we can't expect them to check what scenarios exist and therefore what are welcome. A Bugzilla keyword for reports welcoming an automated test?

This post was posted by Qgil-WMF, but signed as Qgil.

A Bugzilla keyword for reports welcoming an automated test?

I remember we already talked about that, but I am not sure if it is done or not. How do I check if Chris and Andre are following this thread? :)

Željko

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

The only way to know is by asking them.  :(

This post was posted by Qgil-WMF, but signed as Qgil.

Hi

It's a great job... All works and now, I try to do some tests for my extension but Ruby is not my friend for the moment. May be can you help me ?

I describe a little example there : http://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Test_backlog#Table

And my class is :

class PageResult
  include PageObject
  include URL
  table(:tableResult, class: 'wikitable')
end 

And the steps :

When(/^I enter article table :$/) do |tableWikitext|  
  on(EditPage).article_text = tableWikitext
end
Then(/^table should be there:$/) do |table|
  # table is a Cucumber::Ast::Table  
  tableResult = on(PageResult).tableResult
  #DRAGON IS THERE ?
  # tableResult ??DIFF?? table
end

Can you implement this rules ? It will be a good example for newbies.

Thanks karima

Hi Karima,

could you please post this question to our QA mailing list? Most of the people working on browser automation hang out there.

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

Hi

I found :

When(/^I enter article table:$/) do |tableWikiText|  
  on(EditPage).article_text = tableWikiText
end

Then(/^table should be there:$/) do |table|
   nodesTR = Nokogiri::HTML(@browser.html).css(".wikitable tr")
   tableResult = nodesTR.map {|tr| tr.css("th,td").map {|cell| cell.text.strip}}
   table.diff!(tableResult)
end

Bye Karima

This page does not explain when what and how to run tests nor if that's actually needed. All the descriptions of the used tools imply that they are only local things, but then I don't understand how coordination between testers works. Other pages say that only developers should look at the docs on how to run and write tests, which suggests you don't need help running tests.

Quality_Assurance/Browser_testing#How_to_contribute is more helpful, it also links https://wmf.ci.cloudbees.com/

Would you like to see something changed on the page, or did you just want to leave a comment?

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

It's your call to make. :) I came to this page expecting to understand something I didn't manage to understand, but it's possible I don't have to.

All QA/testing pages need some love, we are working on it. :)

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

I am willing to contribute to the QA manual testing team. But do not know where to start from. I have installed everything on the landing page. I clicked on "list of EASY tasks" (from https://www.mediawiki.org/wiki/Browser_testing) and took a look at the bugs recommended for new contributors. but have no clue.can someone help. pls?

Welcome! :)

The easiest way to get started is to join our QA mailing list and introduce yourself:

https://lists.wikimedia.org/mailman/listinfo/qa

http://lists.wikimedia.org/pipermail/qa/2013-May/000003.html

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).