bug tracking

Was reading a litle bit on the net on software testing. This is the term in general. I thought i was working as a tester, now as i see more resources, seems i was more like a bug tracker. We were not testing the system - that were the developers doing. me and others in our department were just recieving pieces of code, installing and imitating user's behaviour to find the bug - the mistakes as we used to call. in this, i would call bug tracking a lower and more narrow field of software testing. we were not using any bug tracking software, except for the one where to register all bugs. first one was from professional developers, where the bug description and its history were kept. then our developers prepare a great software for our company inner needs - task management. we would register the bug and assign the task for the chief programmer. he used to give it to a certain developper to fix it. then we test it and close the task as done if everything was fine.
what is interesting, that there are many blogs on software testing - saw while searching. and there are only a few on bug tracking...

Comments

Alessandra said…
Appreciate you blogging tthis
6:19 AM
Post a Comment

Popular posts from this blog

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Read more

tester's day!

Happy testers day! Top 24 replies by programmers when their programs don't work: 24. "It works fine on MY computer" 23. "Who did you login as ?" 22. "It's a feature" 21. "It's WAD (Working As Designed)" 20. "That's weird..." 19. "It's never done that before." 18. "It worked yesterday." 17. "How is that possible?" 16. "It must be a hardware problem." 15. "What did you type in wrong to get it to crash?" 14. "There is something funky in your data." 13. "I haven't touched that module in weeks!" 12. "You must have the wrong version." 11. "It's just some unlucky coincidence." 10. "I can't test everything!" 9. "THIS can't be the source of THAT." 8. "It works, but it's not been tested." 7. "Somebody must have changed my code." 6. "Did you check for a virus on your system?...
Read more