Go gaga over Machine Learning

One last blog post before the year ends and we start a new beginning in the testing world, this article sums up where testing is headed to! Complexity, testing and its impact on innovation in 2018 Commercial industry has been fundamentally changed by digital technology. The most revolutionary organisations, like Uber and Netflix have shifted the goalposts, moving entire businesses online and introducing accessible, engaging and immersive consumer experiences. And, while tech innovation has historically happened at a discrete product or operational level, today it's taking place across an entire business - and beyond.

One of the best ways to explain micro-services testing - Thoughtworks Testing Strategies in a Microservice Architecture There has been a shift in service based architectures over the last few years towards smaller, more focussed "micro" services. There are many benefits with this approach such as the ability to independently deploy, scale and maintain each component and parallelize development across multiple teams. However, once these additional network partitions have been introduced, the testing strategies that applied for monolithic in process applications need to be reconsidered.

Here is an amazing list of testing ebooks: Note:  This is a work in progress and I will keep adding more eBooks as I find them. It is on git-hub so people can share and contribute. https://github.com/AdyKalra/TestingEbooks Here is a snapshot from github: TestingEbooks All possible testing ebooks Table of Contents Software testing theory Standards in software testing Testing of Free and OpenSource Software Testing with different programming languages Testing Tools Software testing theory Programs and Proofs. Mechanizing Mathematics with Dependent Types. Software testing - Ron Patton Measure Software Quality using Application Security (WIP) - Dinis Cruz The "A" Word - Alan Page Professianal Software Development (Chapter: "5. Software Quality") - Mike G. Miller Acceptance Test Engineering Guide, Vol. I - RC1 A Software Testing Primer (PDF) Classic Testing Mistakes (PDF) - Brian Marick Code Coverage Analysis - Steve Cornett Practical...

Interesting short read on:  Continuous Integration  Patterns and Anti-Patterns  Build Management  Build Practices  Build Configuration  Testing and Code Quality

Last week, GitHub released an awesome feature called Topics. It allows authors to tag their repositories. If you have read my previous post you would know what gitlogs are. Why I love gitlogs is because they innovate and have now updated and built a simple project called Awesome Github Topics .  It's an indexed list of the top 500 topics on GitHub that's painstaking filtered and categorized into different categories based on developer interests. http://www.gitlogs.com/awesome-topics Awesome List of Top Github Topics

Here are a few interesting visualizations that I found while doing research for my talk about testing Insights, also included are the ones that I did not end up using: Open source contributions by location  http://davidfischer.github.io/gdc2/#languages/All GitHut - is an attempt to visualize and explore the complexity of the universe of programming languages used across the repositories hosted on GitHub. http://githut.info/ Who speaks what on GitHub? Visualization 1 is a chord diagram, which indicates the relationship between all possible combinations of programming languages. This data was computed by creating all possible pairs that could be created using the list of 20 languages I have analyzed. By analyzing the combinations, and the number of users that speak both of the languages in question, we get a good idea of what languages are spoken most, but also which languages are 'spoken' quite a lot, but not in combination. It gives a different perspective of th...

Here is the link to my talk at Tconf :

Some of us here are working on the BDD guidelines that should be followed: Would be interested to hear if anyone has thoughts to share: Guidelines Explain in the feature file what the feature is about, just after the “Feature: ” before proceeding to the scenarios (preferably in “In order/As a/I want” format). Write high-level scenario steps by raising the level of abstraction and focus on the “what” rather than the “how” don’t mention UI elements don’t mention ‘click’ or other actions linked to specific UI elements the scenario should remain valid if the UI is replaced with a new UI tomorrow avoid very detailed steps where possible (helps to focus and avoid clutter) Write scenarios using business language rather than using technical language so that it can be understood by everyone. Write scenarios from the perspective of the person who will use or needs the feature (not always a member or user). Use 'I' and explain who the 'I' is in 'Given' s...

I don't know Sathish in person but from what I read here he is trying to raise 60,000 Rs or $1200 ket.to/satish https://in.linkedin.com/in/satishkandikonda Cheers, Ady

It's that day of the year again! Surely every day is Tester's Day, but it feels good to have a special day that can make us testers around the world share and collaborate and feel proud to be one. On September, 9 1945 the scientists of the Harvard University while testing the computer Mark II Aiken Relay Calculator had found a moth which got stuck between the contacts of the electromechanical relay.  The work they performed required some description, and the word had been found – «debugging» (literally: disposal of an insect) – and now it is used to describe the process of identifying and eliminating bugs which cause a computer to malfunction. The removed insect was pasted into the computer log with the entry: “First actual case of bug being found”, and was then transferred to the computer museum. Now that you know, Happy Tester’s day !

Here is an amazing snapshot of a programming competency matrix at different levels: Computer Science 2 n   (Level 0) n 2   (Level 1) n  (Level 2) log(n)  (Level 3) data structures Doesn't know the difference between Array and LinkedList Able to explain and use Arrays, LinkedLists, Dictionaries etc in practical programming tasks Knows space and time tradeoffs of the basic data structures, Arrays vs LinkedLists, Able to explain how hashtables can be implemented and can handle collisions, Priority queues and ways to implement them etc. Knowledge of advanced data structures like B-trees, binomial and fibonacci heaps, AVL/Red Black trees, Splay Trees, Skip Lists, tries etc. algorithms Unable to find the average of numbers in an array (It's hard to believe but I've interviewed such candidates) Basic sorting, searching and data structure traversal and retrieval algorithms Tree, Graph, simple greedy and divide and conquer algorithms, is able to understand the releva...