We have two members in our QA team include me, but senior and I don't have experience about this QA role. Therefore, we had to learn about QA role ourselves. I learned product's functions and working process on qa team during the first year. In second year, I think I should introduce CD and CI if I can.
These are my tasks.
1. Test product (function, performance, UI)
2. Fix bugs
3. Develop new functions
4. Build & Release product
5. Keep VCS(subversion)
1. Test product
There is not specific test. We have only one test checklist that is thirty pages include UI, function and performance to release. It complicated three type of test. There is not unit test. We have tested everything manually. I want to make test automation. Whenever svn was committed, I have to test A to Z manually. It takes so many times.
2. Fix bugs
When bug is reported to QA team, team manager want to fix bugs in QA team.
When bug is come from new source code, team manager also want to fix bugs in QA team. I think bug reports go to man who developed this function is better than come to qa team. I can accept this. But, I want to focus on QA and make CD, CI
3. Support to create new function
Customer requires new functions. Sometimes, I find technique for new functions. I make sample code and explain to software engineer about technique that I found.
4. Build & Release product
Product build manually by Ant at eclipse. This has problems. People must make mistake. If eclipse's environments was changed to do something, building will be wrong. It occurred many time for a year. It must change to automate
5. Keep subversion
We use only trunk branch in svn. It's terrible. All codes didn't test enough to release but, they are committed to trunk. We must use branches. I will make svn's branch strategy and guild this.
[Current work flow]
1. Test
2. Commit Source Code
Most needs
1. Function Test Automation.
2. Performance Test Automation.
3. UI Test Automation.
4. Integration Test Automation.
These spend time a lot. Especially, function test is very important last gate to deploy.
Future Tools
Version Control Tool : SVN
Continuous Integration Server : Jenkins
Issue Tracking System : redmine
Build Tool : ant (hope to use gradle)
UnitTest : JUnit
UITestTool : Katalon Studio & selenium
FunctionTestTool : SoapUI
Code Coverage Tool : Not yet.