Chronicles Of Testing

 How to create an e-magazine tech edition.  The mind-map is self explanatory and includes components and categories/subtopics to help you on your journey in creating a digital magazine. Test it out.

An attempt at collating testing ideas to test image/s inducted for a product. There is scope to add ideas relating to relevant image association, handling missing images, accessibility, securing and addressing the quality of the added image.  Terms of use: If you are working on image induction (single, bulk), image testing, image search, on an e-commerce site this can be used (only) as a reference.  Feel free to find a context to test in various other contexts. Happy testing.

Certain translations that I came across triggered me to add some recommendations to the translator (someone who works on translations) who is yet to recognize or who undermines the value that they create by adding translations. I reckon that it is essential for a translator: Click on the image to view it in an enlarged form. to possess language skills (reading, writing, speaking) to have knowledge of the tools used and  to develop a sense of onus and service to the community. In the above example: The author, Girimane Shyamarao has written a book titled: 'I / Myself, Children and Education' but the translation roughly is made to as you see 'I have children and education'. Such slip can be avoided if we meticulously learn the language, the meaning/s of the words used and in a contextual manner. Some recommendations are now part of the guidelines that I had earlier created when I was involved in translating some educational project for Khan Academy . Than...

There was one occurrence of plagiarism of my work, a blogger by mistake had passed the blog and map I had shared, as their own. I sympathized with that person, if I had mentioned my name or had personalized my work (with a signature/logo) then I would not have put that person in this situation.  I am to blame, as I shy away from making my work copyrighted/add a signature.  My knowledge sources are many.  I refer books, articles, watch videos created by others, learn from many and from their experience.  My credit goes to all who share their learning and in that case, I cannot take credit. Another incident that  triggered me to collate common pitfalls to avoid when we share our work with a wider audience is  when I posted my own work over a year later without revisiting and revising it. A  learner from the community TeemuVesala  reviewed and provided with suggestions to revise it. Thanks, Teemu. Based on these events plus the mind map exe...

Before we proceed: This is not a measure or an estimate of the testing time and effort. Do you have Testers in your team asking for time to test more than what is allotted as time for testing? Ever wondered why Testers need that time and how it gets utilized? Here is a mind-map I put together to capture where I spent my testing effort and time. Is it effective use of testing time?  Answer for yourself. Testers, take a look at the distribution of testing effort and time across the nodes in this mind-map. Do you consider time spent researching, learning and communicating with right sources of knowledge as testing time?  Give it a good thought and action on where you are spending your testing effort and time.  Remember that attendance at meetings and conferences, a talking assignment, interactions with knowledge sources are not time off from testing but to be considered by us testers as testing time so that when we talk to our team we are assertive w...

Lessons learnt when working on a migration project - Pitfalls and Preparations I had not worked on a migration project before. I did not know if testing this project would be same / different from the other projects that I had worked earlier on. I did learn new lessons when I worked on this project and have summed up the lessons learnt in the form of a mind-map below. Note: If several web applications are being migrated it helps to track the progress on each relevant component meticulously. A few other aspects which helped me (in this instance) sail through this project are: Assertive – Being flexible and saying no when needed Asking for help / clarifications in time Learning from mistakes Being practical  Communicating – regularly and effectively Sharing risks early and following it up to its closure (in some instances) Why mind map? Because it helps me collate and share the ideas around a centrali...

Mobile Application Testing - This is not a test first, but prepare to test first approach to testing I) Testing Requirements Begin by gathering the required information to test Credentials – Device,  App, Defect logging Tool [if any] Clarifications – Keep the clarifications log updated throughout the testing phase Deployed code Device – Availability (and unlocked), device details, operating system, build version, charger, adapter, USB Cord Functional Requirement Specification – Obtain information from the development team, previous tester, from the FRS, existing defects, test data, UI screens, known vulnerabilities of the device Context – Learn the context in which the app needs to be tested Scope – Extend / limit testing based on the approaching target time Test Instance – which instance to test on, having this clarified at the earliest is better II) Test Preparation Prepare a check list /Mind map Check access with t...

Mind map on Exploratory Testing a Web Application. The above Mind map summarizes Testing on a Web Application Learnings: Realization about Exploratory Testing Versus Test Case preparation. Writing down test ideas – Relevant and required to capture the missing elements if any. Context is the Queen  Mobile Testing – There is more to it than that meets the eyeball. Web Testing as summarized above in the Mind map. Lessons on Bug Reporting and contextualizing it. Conventional versus My Way of Testing – Every tester has their own Style of testing which needs to be polished. Breaking the bad – Includes breaking one’s own biases and barriers. Being Surprised – Expect to be surprised and not surprised too when you spot a bug on the same page that which you checked and cross checked. Observe, listen, compete, test and report the bug – Pair test and learn with your colleagues. Participate in debriefing sessions. Part...

Here is an image of the mind map (Mind map exported as .png) This version here: Is a screenshot of the mind map by Jing { http://www.techsmith.com/jing.html } Wish I knew few of these pointers on the day one of my testing career - If you ever felt this way, remind yourself it is never too late to learn to think well and to test well. Here is a mind map with aspects to know about software testing, for any aspiring tester on where to begin and the how and where to from here. Each of these points can be extended to include further details.  If you have gone through the mind map and require to know more information, get in touch with any one from the testing world. This post is edited to include the below links. Books to read and authors to be referred.[ http://www.testingcircus.com/testing-books/ ] Blogs to read.[ http://www.huibschoots.nl/downloads/Popular%20blogs%20ALL.pdf ] Twitter - wh...

The  What When How Who  Where of Weekend Testing.  If you have already been a part of weekend testing, then you know where to go looking for learning about the aforementioned WWHWW about weekend testing, if not here is the link: http://weekendtesting.com/ I had heard about Weekend testing chapters of India(WT) facilitated by Ajay Balamurugadas, America(WTA) and  Australia(WTANZ).  Wished to be a part of it and this is where it led me to. What: The what comprises of the mission and the agenda. The mission comprises of what are we testing today? Agenda will be shared by the facilitator and is as below: Introductions - Provide information on where you are from, what do you test and how do you test, your twitter handler - which could be helpful in the Where :) Mission and Charter(s) Open Testing - Test in your own pace. Pair with anyone and perform pair testing, gang up and learn from the wider group. A time check to see if we have enough...