Testing

  • MCET-SEC 6: Schedule / Essential tools

    Since I’m running behind the schedule here with what I wanted to have by now, I thought, I share… this schedule. What I have in my pipeline while creating MCET-SEC – modern cost-efficient toolchain for a small but savvy software engineering company. 1. Modern repository (system that not only holds the source code but enables collaboration – pull-requests, commenting and so on). -> This is done. With one false start  with Gogs, resolved with Gitea. 2. Test Management Software. -> Done and working fine with TestLink. 3. Build server. -> Done with Jenkins. 4. Continuous deployment/delivery. 5. Static code analysis with central reporting. 6. Test automation. 7. Ticketing/issue tracking/time tracking.…

  • MCET-SEC 3: Test Management Software

    My company, CODEFUSION, is 9 years old. We are growing organically. At the time of writing this words (March 2019) we are 14 people.  We are software development company founded and run by software developers. But from the beginning it was clear for us, that the business of software development cannot be successfully run only by developers. We knew that one of the most important aspects of being a software shop is to have good testers. So we hired great testers and quality assurance engineers trying to maintain the 20% ratio (devs to testers). At the beginning they were able to manage their work on foot. We were so few,…