Top 10 BASIC SQL Concepts useful for Database Testing

 Top 10 BASIC SQL Concepts useful for Database Testing

1. SELECT and FROM: This is the “heart” of any SQL query - SELECT columns FROM table.

2. WHERE: This acts as a filter and allows you to select only relevant rows based on conditions.

3. GROUP BY: This helps you aggregate the data by grouping columns.

4. AVG/SUM/MAX/MIN: These are aggregate functions that help you summarise the data.

5. COUNT and DISTINCT: Count helps you find the number of entries and Distinct helps you find unique entries.

6. CASE WHEN: This is a very useful way to create a new derived field or perform complex aggregate operations.

7. JOIN: Join helps you combine data from different tables using join conditions. Please get familiar with inner and left/right/full outer joins.

8. UNION: Union and Union All help you to combine data from multiple tables with similar structure.

9. WINDOW FUNCTION: Allow you to perform calculations across a set of rows.

10. CTE and SUBQUERY: They help you create more complex queries by combining smaller queries.

Happy Learning!😇😇😇

 

TESTING IS LIKE COOKING

Testing a Software is very similar to cooking, according to me being a cooking lover though 😇

I’m not an expert in cooking, but I do know some things about cooking:

• there exist different cuisines
• some dishes are famous only in certain areas
• some dishes need more time to cook, some can be done in minutes
• the correct proportion of salt is a must thing in every dish that we cook

All the above points need to be considered in order to cook a proper dish. To better relate the testing concept with cooking let’s consider an example: Cooking a Biryani.

• the foremost important thing to be checked for is the rice variety that you choose for preparing the Briyani. Briyani goes best with Basmati Rice, many out there would agree with me.
• another fact is you need a proper place to cook the Biryani.
• there's also an important point of the rice to be cooked only 80 percent before giving it a dum.
• there's also a need for a proper vessel to cook the Biryani, so it requires a wide thick bottom vessel.

These facts make me relate to an acronym: BELT, for Bait, Equipment, Location, and Timing (Read in an article online). Let’s use this in our later points.

All the above conditions have to be met in order to prepare a delicious yummy Biryani. If even one goes wrong, there would be a major mis in Briyani that was expected...

In the same sense, when you begin to find for a bug, consider the below points:-

• not all bugs are the same there exist different varieties of bugs. What kind do you want to find?
• you can’t find a bug everywhere. Where are you looking for bugs? 
• some bugs only exist at particular times. Are you looking at the right time?
• some bugs won’t reveal their presence unless you provide the right stimulus. Are you using the right tools and data for the job? 

So back to the BELT acronym that I mentioned before - Bait, Equipment, Location, and Timing. Let’s co-relate software testing to this acronym...

Let’s say the variety of bugs you’re looking for is a crash in a Web application. Crashes can be triggered when bad data is passed between functions, or if the application reads something wrong.

1. What would be the bait in this case? Does the application read data in from the command line? A file? A database? A network?
2. What would be the equipment? What tools will you use to assist in finding this bug? 
3. Where would an ideal location be? Where would you expect to find this type of bug? At the application’s entry (such as initially reading a file), or deeper in the code (arguments passed between functions)? The approach would be different depending on where you’re cooking :-)
4. When would you expect to find these issues? Is there a particular time you might find a crash? Does your application behave differently at certain times of day, or when certain other events are happening?

The above questions will help you to a better approach to testing.

Hopefully, this has helped consider what kind of bug you’re looking for, and don’t forget your cooking BELT.

Happy Cooking!

ISTQB - CTFL Guide

Hi Folks, It's been quite a long time posting in our blog.

Someone rightly said "Learning is a never-ending process", for the past few months got busy with my ISTQB-CTFL Certification preparation, a long time to do the task. With 3 months of continuous study and preparation happy to share that I cleared the exam and now can proudly say that I'm a Certified Testers 😊

There would be many Tester's around who would be in the pace of ISTQB preparation, so thought of sharing some key points from my learning phase.

1. Know about ISTQB Certification

Software testing certification demonstrates your knowledge and skill. The leading software testing standard is ISTQB software testing certification. That’s why ISTQB software testing certification is used in more than 100 countries making it by far the #1 software testing certification in the world.

Before we start let's check out the steps towards this ISTQB certification 😊

5 Steps to ISTQB Certification:

1. Start by learning about ISTQB Foundation Level Certification.

2. Then study for the ISTQB exam using the free ISTQB syllabus, sample exam questions & answers, and glossary of software testing terms. Or you can choose taking an accredited (proven) software testing training course.

3. Next, register for your exam through ISTQB exam provider. 

4. Finally, pass the exam. Excellent! Once you clear the exam you will be added to the ISTQB successful candidate registry. You can now proudly display your software testing certificate and include your certification on your resume, stating that you are on the official ISTQB Certified Software Tester.

5. Keep moving up. Look at the Software Testing Career Path to see where you should take your career.

Pictorial view of the certification path:

Happy to promote : WOMEN IN TECH GLOBAL CONFERENCE 2021

A highly engaging conference bringing people together to share knowledge, experiences & thought leadership.

WOMEN IN TECH
GLOBAL CONFERENCE

Women-Tech-Conference

#womentech #womentechglobalconference2021

Happy to promote this great event 😊

The Test Chat Community - 21 Days 21 TIPS

Being helpful means providing something of value so your audience comes to see you as a trustworthy and reliable resource. One such resource in recent times I witnessed is the "The Test Chat Community" The idea of The Test Chat is based on the fact that testers do not have an opportunity or platform to talk, discuss our problems, and overcome those challenges, practical situations, misconceptions about testing, and most importantly have fun.

2 months ago The Test Chat Community brought up a challenge of 21 days 21 tips? Where we need to share 1 tip with other testers for the next 21 days and we'll see there's a whole bunch of great tips after 21 days.

As a member of this community, I too shared my part. And to my surprise after 21 days of this challenge, there was an e-book released with all tester's ideas in one place. So why wait checkout the e-Book with great ideas loaded 21 Days 21 TIPS

Here is my part do checkout 😊

Happy Sharing 😊