(Please set yourself as task assignee of this session)
- Title of session: Software testing for developers
- Session description: Meet members of the Wikimedia Quality and Test Engineering Team (@Ryasmeen, @dom_walden, @pwangai, @zeljkofilipin) and chat about software testing.
- Username for contact: @zeljkofilipin
- Session duration (25 or 50 min): 25
- Session type (presentation, workshop, discussion, etc.): discussion
- Language of session (English, Arabic, etc.): English
- Prerequisites (some Python, etc.):
- Any other details to share?:
- Interested? Add your username below
Notes from session:
Software testing for developers
Date and time: Saturday May 4, 2024 14:30
Relevant links
- Phabricator task: https://phabricator.wikimedia.org/T364200
- Session slides:
- https://www.mediawiki.org/wiki/User:DWalden_(WMF)/Testing_heuristics
Presenter
@zeljkofilipin
Peter
Rumana
Dom
Participants
Notes
QTE team divided into - Test Engineer group and Software Engineers. Zeljko maintains frame work and browser testing infrastructure.
Dom - Test Engineer for community tech and trust and safety teams.
Peter - Promote use of xxx in the foundation and one of the tools used is Sonarcloud. Working on integrating extensions into Sonar cloud, 70% done with integrating production extensions.
Rumana - Responsibility to prioritize the tests and create strategy on how to test & prioritize testing
The team has a blog post writing club (https://phabricator.wikimedia.org/T263660) to encourage each other to write and publish a blog post. QTE Book club (https://phabricator.wikimedia.org/T247665) since 2021, every few months they pick a book and it takes 1-3 months to complete the book and then take selection from the team on next books. Read all the fundermental books on Software Testing.
Questions
Q: Is there a configuration file you can put in a repo for sonarcloud?
A: Yes, create a properties file and adjust your settings before scanning. If you want to ignore certain files you can use sonar.properties to ignore.
Q: When you test for other teams whats your requirements for instrustions for you so you know what to test? User Story?
A:I would need to know where to test and useful to have some kind of central requirements. Which code was changed? What features and funcontionality would it affect?
Q: Do you have the appetite to come up with these instructions?
A: Experimented With Coming Up With Guidelines For Writing And Requirements On Testing Its Difficult To Set These Cos They Are Generally Incomplete
Q: Are they public office hours.
A: We can invite people to the office hours but thinking of how to make it accessible. This is a great way to help move the work forward.
Q: Whats your take on the "make sure nothing broke" kind of tasks?
A: We get these kind of tasks and the kind of instructions that help is sharing which areas to check or which areas have undergone refactoring to help with the testing.
Q:
A: