some thougths

looking at this testing blog and thinking it is awful... shame on me.
the last time i talked with my boss, he mentioned they are thinking about me back for work. (staying at hoem with my babay daughter). so, it may be i will be back testing in a year or sooner... God knows. and maybe this blog will become richer and more attractive...

Comments

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 ask for
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

embedded software testing

I have got a chance to work at previous www.aitecs.com, now Moog as software tester for five months. Worked with software for infusion pumps. It was a great experience for me as a tester and want to share with some impressions. 1. Same rules. The first lesson I learned that same rules for testing apply everywhere. Embedded software frightened a little. I thought it should be very different, and I do not know how to test. I learned that all the rules that apply to web site test, application testing, also apply to embedded software testing. Testing the software of infusion pump got me back to pure testing. Analyzing the new functionality, applying mixed of black and some white box methods, searching through requirements made me feel real tester. 2. Validation. For me verification and validation used to be only theoretical expressions. And not clear enough what they mean. I have been testing a few IT projects and mainly worked with verification. Used to verify the software is made accord
Read more