SOFTWARE TESTING

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 ...

My previous employer organised internal security training for QAs. As coming not from development background, they were good, but too tough for me. There is really good free resource on pluralsight.com by Troy Hunt " Hack yourself first ". It is declared for developers to deepen their knowledge of security. Myself I found it really cool as the author explains everything clearly with good examples.

There was time, when I found out about Selenium IDE, simple add-on for Firefox and used it for a while. Had issues with long tests, questions splitting workflow into some pieces, manage page loads, introduce sleeps..  Cool thing for manual tester.  Then webdriver was introduced, IDE was considered a bad thing in my group :) Starting working in new project and still having only few screens with mocked data for a few weeks. That means re-clicking every button for regression, or giving health-check clicks that both environments are still ok  or  are again ok to use. To set up custom project with web-driver seemed too many efforts - and the selenium is so cool again! Half an hour of work (ok, maybe an hour) and clicking buttons for me in  slow run mode :)

Adding Gremlin  to my TODO list to install and explore. Colleague was happy about its non stop clicking abilities :)

Nice picture to remember what I have to do :) Following the thought, regret and changing focus from quality would be the real enemy for the tester. The work is not efficient if I start thinking : oh, this is one more trivial usability or minor functionality issue. No one is going to fix it, so no point to worsen our unit's bug statistics by registering it; we need to release quickly in order to finish sprint successfully, so quick shallow testing will be enough - do not want to be bottleneck in my team's performance; loosing motivation to write automated tests or dig into technical stuff after being criticized by seniors. Oh sorry, that is called review and tough character. Quality of tests and skills is also important...  

In my company's techblog, mainly developers are contributing. While browsing across some links in the web, found that companies own pretty interesting tech blogs, sometimes filled with testing or QA relating stuff. Pretty cool to see one more resource to get insiders insights - how do others test, assure quality or handle challenges :) Some links from Linkedin , theGuardian   and Shutterstock  .

As I notice my personal emotional reaction for such kind of comments (above the picture), time to start blogging my testing journey again  :)

Was looking at the recipe of pancakes. Cannot understand what the ingredients are :)

one more video on testing. serious one by James Whittaker

6th Annual Google Test Automation Conference 2011 (GTAC 2011) "Cloudy With A Chance Of Tests" Computer History Museum Mountain View, CA USA October 26-27, 2011 Opening Keynote: Test is Dead Presented by Alberto Savoia More on testing from google

Over the last five years the supply of resources in the web slightly changed. Earlier there were only articles available. Therefore today I would spot the best knowlegde sharing form - webinars. Here is a link to StickyMinds webseminar s - higly recommend to find How Google Tests Software Presented by: James Whittaker, Test Engineering Director, Google. Won't regret! The material presented in webinar may be found in new book by three google co-authers: James A. Whittaker , Jason Arbon , Jeff Carollo

Reporting status on ISTQB advanced test analyst certificate: preparation in progress. Almost finishing reading the book , then will try another one . Do not feel very exciting while digging into testing theory - in my current position I do not use a lot what I read about. Just taking care of my present and future as a tester. Would be nice to be certified. On of the best sites found recently - softwaretestinggenius.com . Full site of pdf download, ISTQB sample questions. Sample exams could be the latest phase of preparation for me - after the Books. Any recommendation? http://www.softwaretestinggenius.com

Sometimes, as a user, I report bugs on various systems. Very seldom, ussually by support email. Today opened my google adsense account after a long break. Was surprised by new feature on the top right menu 'Report the issue'. As a tester, of course I tried it without sending the real issue to google. Wow! As my colleague said 'Respect'. Really nice and user friendly feature. A load for support people should be higher to review the screen images. On the whole, the time should be saved for questions / answers and time for getting 'what did they mean by this'. The images will give more info :) Really cool thing.

Early call for paper - Theory and Practice of Software Testing (TAPOST 2011), 12th International Conference: Forming Basis of Globally Mature Testing. When: Riga (Latvia), May 26, 2011

Have registered to utest.com a few years ago, although have not tried to test any of the projects there. Have you? What I found recently - the utest blog , full of interesting articles and interviews. Recommend.

short pdf with slides on agile testing . hot topic for me.

Two months ago I joined scrum team in another company. Sharing the video I really enjoy about scrum:

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...

Baltic testers invited to conference "Theory and Practice of Software Testing", 11th International Conference 'Discover the Tester in You' - July 6, 2010 in Ryga (Latvia). Call for papers announced: two types of presentations are planned – short (15 minutes of talk, 5 minutes for questions) and long (30 minutes of talk, 10 minutes for questions). The submission should include a meaningful abstract of your presentation (up to 3 pages), indication of presentation type (short or long), a short biography and full contact details. Language – English. For more info on topics look at is.lv website. I am interested in suggested topic: Embedded software testing challenges, tips and tricks: Testing embedded software. It would not be correct to present topic on project I no longer work with, so will try to make a longer post here later.