Posts

Showing posts from 2018

Session-Based Test Management

Image
New Goal in My Learning University:  Boost Your Testing Super Powers to Exploratory Testing. My Learning Notes -  Day 04: Session-Based Test Management (Part-2) In Previous Post  Day 03: Session-Based Test Management , We have learnt about SBTM and Elements of SBTM. Today, I learnt about Product Coverage Outlines (PCO), Importance of PCO in SBTM, Different Types of Test Sessions, Session Debriefing and Structure of the Meeting. Reference:  Session-Based Test Management article by Jonathan Bach -http://www.satisfice.com/articles/sbtm.pdf Do something painful today that your future self will thank you for!

Session-Based Test Management

Image
New Goal in My Learning University:  Boost Your Testing Super Powers to Exploratory Testing. My Learning Notes -  Day 03: Session-Based Test Management It is a long process to learn and understand Session Based Test Management. In Previous Post:  Day 02: Brief History of Exploratory Testing , We have learnt about History of Exploratory Testing and Introduction of SBTM. I have prepared my notes based on my learning about SBTM. (3rd Dec - 7th Dec). I have used Mindmapping tool (XMind) to make my notes. Note: This is not the final version. PS:  Please feel free to write to me personally for any corrections. References:  http://www.satisfice.com/sbtm/

Brief History of Exploratory Testing

Image
New Goal in My Learning University:  Boost Your Testing Super Powers to Exploratory Testing. My Learning Notes -   Day 02: Brief History of Exploratory Testing It was a long process to learn about History of Exploratory Testing. The story on ET is the most important learning I’ve have done today. References:     http://www.satisfice.com/blog/archives/1509 http://www.satisfice.com/blog/archives/1504                                     Believe Yourself. Reinvent Yourself. 

What is Exploratory Testing

Image
New Goal in My Learning University:  Boost Your Testing Super Powers to Exploratory Testing. My Learning Notes -   Day 01:  What is Exploratory Testing? What is Exploratory Testing? Exploratory Testing is an approach to Software Testing. It is sometimes more productive than Scripted Testing. We at least unconsciously perform exploratory testing. How do we perform Exploratory Testing? In Exploratory Testing, We test design and test execution at the same time. Not defined in Advance. In Scripted Testing, We predefined procedures (Manual / Automated). Exploratory Testing != Adhoc Testing Exploratory Testing is done in a specific way to verify specific facts. Exploratory Testing is a structured Process. Whereas Adhoc Testing is not done in a specific way nor to verify specific facts. Adhoc Testing is unstructured Process. Term “Exploratory Testing” is coined by Cem Kaner in Testing Computer Software as Thoughtful approach to Adhoc-Testing. Balance

Find 5 API testing experts to follow on Twitter.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 17th Challenge:  Find 5 API testing experts to follow on Twitter. I follow below 5 API Testing experts on Twitter. Lorinda Brandon - https://twitter.com/lindybrandon (First Person I met and Learnt about API and API Testing) 👈 Matthias Biehl - https://twitter.com/mattbiehl (Author and Advisor at API University) Mike Amundsen - https://twitter.com/mamund (Director of API Academy) Ole Lensmar - https://twitter.com/olensmar  (SOAPUI Creator) Abhinav Asthana - https://twitter.com/a85  (Postman Creator)                                  What are you doing to get better? Invest in yourself.

Compare and contrast mocking, stubbing, and faking.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 14th Challenge: Compare and contrast mocking, stubbing, and faking. It is one of the challenging topic to understand related to Unit Testing. Test Doubles (Mocks, Stubs, Fakes etc.), are an essential tool when writing unit tests.  A test double is an object that can stand in for a real object in a test , similar to how a stunt double stands in for an actor in a movie for dangerous scenes.  The most common types of test doubles are stubs, mocks, and fakes. Their purpose is to be substituted for dependencies of the class or classes under test. Example: E-mail services are a canonical example - we don't want to send out real e-mails eve

Contribute to the list of API automation tools over on The Club and share your experiences with using them.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 13th Challenge:  Contribute to the list of API automation tools over on The Club and share your experiences with using them. I am not into Automation of (UI/API) levels. So, this challenge helped me to uncover different tools used in Testing the APIs. I always reach out to this website to learn related to Automation. Joe writes posts which focuses on Automation -  https://www.joecolantonio.com   There are different API Testing tools which we can use to Automate API Testing. Postman 👈 Karate DSL 👈 Soap UI 👈 HTTPMaster Express Rest-Assured 👈 RestSharp RestConsole RoboHydra Server Hippie-Swagger WebInject Pyres

Share what skills a team needs to succeed with API testing.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 12th Challenge: Share what skills a team needs to succeed with API testing. While I have started learning about APIs and API Testing, while working at Unilog. Below are the skills a Team/Team Members needs to have to succeed with API Testing. Have Curiosity to Learn and Research. Able to understand Business Requirements with Functional Requirements Able to Collaborate and Communicate with Developers Able to Read the API Documentation if readily available (or) Find them Online. Testing Skills and Mindset how to Test with various conditions (rationally/logically). Able to Plan the testing activity and Inform the relevant stakehold

Learn about different types of API’s, share your findings.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 11th Challenge is  Learn about different types of API’s, share your findings. There are different views on Different Types of API's. View #1: APIs come in many shapes and sizes. Even when APIs may share a common resource, the likelihood that they are similar in functional. We can organize API's into different meaningful groups. Different Types Of APIs: General Data  - You can get at data across the platform, users, and resources. Relative Data  - You can get at data that is relative to a user, company, or specific account. Static Data  - The data doesn’t change too often, and will always remain fairly constant. Evolving Data  - The data chang

Share your favourite API testing tools and why.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 10th Challenge is  Share your favourite API testing tools and why. In this blogpost, I have written about Tools that I have used and My Favorite API Testing Tools. When I started my career at Unilog, We had Internally Developed tool "EclipseTest" to make requests for Epicor Eclipse ERP. That was the starting point for me to learn about APIs. Then I had worked on SOAP Webservices which interacts with Infor SX.E ERP. Here, I had been introduced to SOAP UI. SOAPUI Tool : 👍 I have used Open Source version. It was very useful in testing the SOAP Webservices. Download:  https://www.soapui.org/downloads/soapui.html Then I had worked on REST

Share some tools we can use to discover what API calls our applications are making.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). 9th Challenge is Share some tools we can use to discover what API calls our applications are making. I have started working with API's in my earlier company (Unilog) in the year 2014-15. Where I have worked on SOAP Webservices which interacts with Ecommerce Web Application. I was initially provided with WSDL, without prior knowledge of what it is. I have started going through SOAP UI Tutorials to learn How and What it interacts. ( https://www.soapui.org/soapui-101-beginners-guide-api-testing.html )   Used API Documentation of ERP as a basis to learn about API Calls and functionality. Later learnt about usage of Web Developer Tools - Network tab. This

Explore the API thread on The Club and contribute to the conversations.

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). Eight Challenge is  Explore the API thread on The Club and contribute to the conversations. There are lots of Questions and Conversations on API and Testing. https://club.ministryoftesting.com/c/all-testing-talk/api This provides access to the Threads, helps to understand and have different ideas on Testing.    I have contributed to the conversations on below thread. https://club.ministryoftesting.com/t/need-to-learn-soapui/16286/7 If you believe in yourself and have  dedication   and pride - and never quit, you'll be a winner. ...

Complete exercise one over at The Club using popular API testing tools such as Postman, SoapUI, and API Fortress

Image
Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge. This time topic is on API Testing. Challenge Link:   https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing    It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015). Seventh Challenge is  Complete Exercise one over at The Club using popular API testing tools such as Postman, SoapUI, and API Fortress. https://club.ministryoftesting.com/t/30-days-of-api-testing-day-7-complete-exercise-1/19622 Goal Execute some simple API calls using as many tools as possible! Objectives Send a GET and POST request Gain exposure to many API testing tools Exercise Choose an API testing tool such as  API Fortress ,  Postman ,  SoapUI  ,  Paw  or perhaps a different one. Complete the GET and POST call on a test API. Example Using  https://automationintesting.online  created by Mark Winteringham and Richard, do the foll