Software Testing

Update & Share tips on Testing, Develoment, Design & Other New Tech Trends

Post Top Ad

Post Top Ad

Thursday, September 27, 2018

September 27, 2018

What is ISTQB and its benefits?

The demand for testing in the quality assurance industry is on the rise nowadays. According to the World Quality Report 2015-16, the budget for quality assurance is going to reach 40% of the IT budget in 2018, so you can understand why many people are finding their way into this promising field. One of the ways is to obtain a manual testing certificate.

These certificates provide proof that someone has somewhat knowledge and skills in software testing. Right now, one of the most popular testing certification in the world is ISTQB.

ISTQB stand for International Software Testing Qualifications Board - a non-profit organization issue thousands of internationally recognized certifications over more than 70 countries. That why, In this article I will focus only on it.

OSTQB. testing, tester,
ISTQB and ITS BENEFITS


Type Of ISTQB

Foundation level certification

The only criteria are to have 6 months experience in the testing position. This level demonstrates the understanding of the basic concepts of software testing. Anyone can take it, even if you have nothing to do with the IT industry.

The syllabus covers six main topics:

  • fundamentals of testing
  • testing in the software lifecycle
  • static techniques like reviews
  • behavioral (black-box)
  • structural (white-box)
  • test design; test management and testing tools.


Advanced level certification

This level is designed for at least 5 years practical experience in the testing role. The syllabus is divided into three main areas:

  • advanced behavioral or black box testing and testing standards for business-oriented testers
  • test automation and advanced structural or white box testing for technically-oriented testers and programmers
  • sophisticated test management concepts for managers.

Expert level certification

Design for those who have at least 8 years experience as a tester.

Now you have understood its structure, I want to go deeper into why you should get an ISTQB certification. Below is some reason:

As I have mentioned above, testing certification helps the new start in the Software QA world. Most employers will consider a good certificate as an important criterion in the resume. To obtain one is a plus point in your resume and make you stand out compared to other competitors. When you prepare for the test, you don’t have to take any expensive course. You can self-study, hire a trainer or use ASTQB-accredited education, whatever works best for your finance.

The advantages of ISTQB certfication


It also helps tremendously with professionals who have years of experience. ISTQB Certification helps you gain knowledge about the standard testing definitions and updated technology, so you can have more opportunities to enter a new market. But the most fundamental benefit is to help skilled tester reduce defects.

For software development companies, these certificate help reduce cost and offer greater efficiency and speed, and higher software quality since it’ll be able to reach to knowledgeable and skilled employees. Your companies can also qualify lower tech insurance costs if you hiring ISTQB certified employees.

However, I hope you understand a manual testing certification like ISTQB can’t be enough if you are looking for growth in this technology world. It can be a great extra to your profile but if you want to get somewhere, you must keep learning new things and keep up with all new innovation.

Wednesday, September 12, 2018

September 12, 2018

How to Become a Software Tester?

Software testing plays a critical role in the quality and usability of the final product. Testing at times is a demanding position on the rise. If you are one of those who wants to have a foot in, then you have come to the right place. This post will give you an insight on how to become a software tester.

What is a software tester?

They are the quality assurance experts who root out bugs and save end user from poor performance and highly buggy software or application. They are a part of what builds a good company image for decreasing support calls from frustrated customers.

software tester, testing software,
How to become a software tester

How can you become a software tester?

1. Education Background and Training

Many employers look for candidates with a bachelor’s degree in computer science, software engineering or related to math field, although that’s not always the case. There are still people getting into this job without a college degree. If you do not hold any of these degrees, then you can complete a software testing certification like:

  • International Software Testing Qualifications Board (ISTQB) - This is one of the most the popular software certificate in the world - an excellent investment that makes your resume stand out.
  • Rapid Software Testing (RST) - a methodology focus on testing software.


It is not mandatory, but most of the companies have this criterion. Having this will give off an excellent impression and ensure a better chance to land the job. A newbie can also find internship programs to give you a good experience. Maybe you will have to work for free but try your best in this position because a letter of recommendation and influence reference is going to help you wonder.

You need to have a solid background in this field in other to excel in this. Most people work in the tech industry must have self-learning skill, a strong passion and a mind of curiosity. There are many open resources for tester out there for you to explore. Try reading good books, blogs or articles about software testing,  working on various tools, keeping up with the latest trends.

2. Find a job.

According to the World Quality Report 2015-16, the budget for quality assurance expert in tech companies is going to reach 40% in 2018. This has indicated that software testers have become promising jobs at the time. If you want to become a software tester, then you should prepare as soon as possible, not just about knowledge but also about your non-technical skills like critical thinking, analytics, communication, etc.  

You should start spending time browsing jobs sites like Linkedin, Indeed, and Dice. Make sure to have a well-written, scannable resume, and you’ll better consider composing a cover letter before sending out applications. Practice mock interviews. Take the feedback and fix the issues after mock interviews.

Here a small tip: if you are finding the job when having little experience than your attitude is what difference you from other candidates. Don't worry too much since you are a newbie in this field employers won't expect you to know complex ideas.

Testing can be an exciting area since it doesn’t focus on just one particular technology. But, in the end, what matters the most is the pure passion that will lead you to success if you truly want to become a software tester.

Wednesday, February 21, 2018

February 21, 2018

What You Actually Need to Know About Software Developer

What You Actually Need to Know About Software Developer: What does a software developer do? How much they make and what make them different from software engineers? This article will give these answers.

what do software developers do




Becoming a software developer is not easy. Any student before choosing this profession would have thought so.

More than just theories, or programming thinking is programming. For the software developer sector, you will need a lot of knowledge, skills, good programming background. More practice is equally important.

To be able to explain all of this vast array of knowledge, I would like to share this article with you. The article is a collection of topics about software developers. It helps you understand the daily work of a programmer, it also provides you with the relative salaries they receive depending on the region, experience and country.

The Savvycom article also offers some confusing concepts, and helps you distinguish them. For example, do you know why software developers vs engineers are different?

To solve all the questions in your heart, take a moment to read the article below. And then discuss it later. What You Actually Need to Know About Software Developer

Friday, February 2, 2018

February 02, 2018

What is difference between QA, QC and software testing?

As the tester grows, along with the demand, the interview questions in this profession are favored to learn more. In order to apply successfully to large companies, you need to prepare well, skills, knowledge to interview about tester..

Read more: 20 Best Software Testing Interview Questions




To be a good tester, not only do you have to have in-depth knowledge of the profession, but also the ability to explain the terminology to help others understand the difference. Perhaps that is the basic knowledge, that anyone who wants to do this industry should learn thoroughly.

  • Read more: Difference between QA and QC in testing
To answer this question: What is difference between QA, QC and software testing. Firstly, we should understand the definition and role of them to see it different from other.


Quality Assurance (QA) refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA track the outcomes and adjusts the process to meed the expectation.

Quality Control (QC) concern with the quality of the product. QC finds the defects and suggest improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

Thursday, February 1, 2018

February 01, 2018

Software engineer vs associate vs senior software engineer are different or not?

Talk about the differences between software engineer vs associate vs senior software engineer  . There are some terms that people in the profession can not quite understand. So, today's post is written with the desire to unravel these questions and concerns. This is also intended for those who do not have the technical background knowledge to have an opportunity to better understand the industries they would like to become part of.

Specifically, we are talking about three notions that are making people unhappy: software engineers, associated software engineers, and senior software engineers. Looks like we can clearly classify these three specialized terms. But these terms is different way from this comparison: the comparison between web designer vs web developer


senior software engineer, associate software engineer, software engineer
differences between software engineer vs associate vs senior software engineer

Anyone who understands these three phrases would have a common opinion and confirmed that these three concepts correspond to the level of proficiency of the skills, knowledge and experience that correspond to the level of work. 

First, associated software engineers refer to software engineers with relevant skills, but they do not have the skills needed to interfere deeply with the decisions or system tasks. They are often the ones that need careful consideration, and guidance rather than self-made from a-z.

About the difference between them, these two terms are meant to classify candidates with long experience, and candidates with little experience in the profession. The role of this classification, which affects the salaries, bonuses, and responsibilities of the team as a whole. 

The associate software engineer and under senior engineers are software engineers. These are the people who have the ability and skills to perform, complete a level of work.

Senior software engineers who are capable of self-responsibility for the whole system, the ability to self-judge and make important decisions, in case of need. And those who have higher salaries than both. Because of the experience, skills, they are more professional.

And read more: The difference between qa and qc in software testing

Friday, January 12, 2018

January 12, 2018

How To Make A Powerful Risk Management Template

The template is formatted nicely for you in the link at the end of this post. I also want to state, nice and early, that this template is adopted from a MSF document. It has proven itself a nice risk management template for me in a variety of software situations and does not tend to overwhelm anyone. Even clients who lack technical knowledge tend to get it and appreciate it.

These are the column names and description of what information goes in the columns. The .xls contains all this information and looks nicer. I cannot present a table well within WordPress. Sorry about that. Go ahead and use it. Say nice things about me if you like it.

Make a powerful risk management template

Risk Management Fields:

  • Risk ID: This is a simple numeric identifier for the risk. We have to keep track of each risk, independently.
  • Description: Summarize the risk. What is the issue at hand, who and what are the players involved, what is the concern? Be as high-level as you can be. No need to get bogged down in details here. Document what is immediately relevant and make sure that the Risk Owner has full understanding. This document should provide an overview for stakeholders but not overwhelm them with detail or technical information.
  • Impact: If this risk becomes a reality, how big of a deal will it be? Obviously, this is subject to a degree of context. Some teams may feel that not building RSS feeds into their System is a horrible misfortune, because their SEM campaign depends upon it. Other organizations will not be overly concerned with RSS feeds, since all their content is reserved for members. Use 1-3 for “not a huge problem”, 4-7 for “considerable problem”, 8-10 for “major problem”, and 100 for “showstopper”
  • Probability: How likely is it that this risk will manifest as reality? This may be tough to determine, but look at Historical Information, talk to your experts, and nail down your best estimate. This will be a percentage: 1% to 100%. If it is 100%, immediately consider the risk triggered and look to the contingency plan.
  • Exposure: Impact times Probability = Exposure. You need to do a little math here, sorry. This will represent how “exposed” your project is to the risk. Do you have a gaping hole in your armor, or are you pretty well insulated against tragedy? At minimum, this lets you see what the biggest risks are. Leveraged a bit more, it can show you what risks are truly worth immediate consideration and action.
  • Contingency Plan: What are you going to do when this risk becomes a reality? This is your backup plan, and it doesn’t hurt to have more than one. It does, however, make sense to have a primary contingency plan because you are going to have to take definitive action when the time comes, and you don’t want to have a bunch of meetings to determine the next steps. Congingency plans should be as unrisky as possible. It makes no sense to lay out a contingency plan like “Fly to Mars and find the secret element that will save us.” Write up a primary backup plan, and note others if you have identified them. Do not, however, spend too much time coming up with alternates. You want one safe Contingency Plan.
  • Trigger: What will tell you when this is no longer a risk and is now a reality? Usually, the trigger will be an event or a set of conditions. When the trigger event occurs or the trigger conditions manifest, you immediately move to your primary Contingency Plan. There should be no wishy-washy triggers. A trigger is a trigger, and when it is triggered, you take action. Just like a gun. When you pull the trigger, you can’t debate the bullet. I mention this because when it comes to HR or other sensitive issues, people may waver.
  • Risk Owner: Who is responsible for keeping tabs on this risk? Usually I recommend that the PM is the Risk Owner, but it may make sense for someone on the development team (like the Dev Lead) to be the Risk Owner. They may have intimate knowledge of the System that the PM does not have . I have seen the Risk Owner be the PMO, in which case they better not be too busy.
  • Mitigation: What are you going to do to make sure that the risk does not get triggered? Essentially: how are you going to control the risk? This will come from conversation with your stakeholders. I recommend having a Risk Assessment meeting and bringing key stakeholders together. Add the mitigation field as you go, but call it what you want.”Mitigation” is a very formal term.
  • Adjusted Impact: With your Mitigation and Contigency plan, what is the projected impact of this risk?
  • Adjusted Probablility: With your Mitigation and Contingency plan, what are the chances that this will still happen? Again, this is meant to measure the value of your Contingency and Trigger.
  • Adjusted Exposure: With your Mitigation and Contingency plan, what would the Exposure be? This is meant to make sure that your Contingency Plan is an effective one.
We hope this is useful for someone. It has been adopted from Microsoft’s Solutions Framework, streamlined and changed a bit. I find this more universally applicable.

Wednesday, November 29, 2017

November 29, 2017

Top 24 Testing Interview Questions For Best Preparation

Have a good preparation for Testing interview for a good job is needed. There are many questions on the internet. But You should focus on important questions for your future career. Here are top 25 testing interview question., brought up by softwaretestingprinciple.

Top 24 best testing interview questions

1) How well do you handle ambiguity?
2) What is your mentality toward automating tests that are currently being done manually?
3) Explain how you differentiate a symptom vs. a cause when testing.
4) Are you willing to stand up to developers who disagree with your results?
5) Are you willing to cut corners to save time?
6) Can you explain the SDLC and Agile methodology?
7) Explain your attitude toward documentation. Do you believe more is better? Why or why not?
8) What do you think of learning a new product?
9) How well do you work with colleagues?
10) Do you think software tester is a perfectionist?
11) How well do you work under pressure situations with deadlines?
12) Tell me what is your experience with developing corner cases?
13) Do you usually catch up with current technology trends? Why?
14) Tell me what motivates you most?
15) What are your ultimate career aspirations?
16) One sentence describes you most. What is it?
17) What brought you to this testing position?
18) Which fields do you think our company could do better?
19) Tell me the reason why do you want to work for us?
20) What testing methods are you familiar with? Do you have a favorite? And why?
21) What is the difference between Performance Testing, Load Testing, and Stress Testing?
22) What is a test Plan? What does it include?
23) Can you tell me what a Use Case is?
24) What is Business Requirement Document?

Wednesday, November 22, 2017

November 22, 2017

Is the difference between Junior and Senior Developer only in years of experience?

Many people think that the difference between Junior and Senior Developer is only in years of experience. And Junior is a newcomer, with some years of practical experience.. Senior develoepr with many years of experience. So they are better than those new to the software development.

However, the real difference is not just there. For the developer, Senior will understand that it is a job that requires him to look for solutions to the problems. The Junior understands that he is working with lines of code.

Senior vs Junior Developer

The information technology industry has developed, leading to higher demand. However, the efforts to recruit trainees with the desire to meet and reduce costs whether there is a good solution for this? Or just a few experienced people to give them the lead? What do you think will make a difference here?

What is the job of a Junior developer?


Junior, as mentioned above, is a young, newly graduated coder who is more equipped with theoretical knowledge than practiced, who need more real-world experience to be able to work well in the industry.

As a junior developer, what you need to keep in mind is focus on coding, you do not need to care about how far the user experiences this application, whether it's relevant to them, or the rationale. other.

Junior developers usually only do one stage of the software development process, like code or something.

What is the job of a senior developer?


Senior, deep understanding is a person with good skills, perennial, knowledgeable, and can participate in many stages in the software development process. He can make from A - Z as involved in software design, customer contact, product development as required, to software maintenance.

In general, the Senior requires a greater amount of knowledge, more skills. A senior also has the ability to manage projects, and split tasks for the team (as the leader of the project).

Here, you know the difference concept of senior developers and junior developers that we are very confused in the past. In general, both of them are based on the same, however, when applied, it is a very big difference.