Blog

, page 3 back to homepage

Forget the password? Then scan your finger 0

How do you unlock your smartphone? Do you enter the password or use fingerprint authentication? How do you confirm a transaction in your banking application? Do you enter a correct

Read More

How not to miss the last bug? 0

After product release, users find a serious bug despite much time and efforts spent on coding and testing. How and why does this happen? Now we are going to find

Read More

Shift-right or shift-left? What testing to choose? 0

Are you sure that shift-left testing is a new approach? Actually, in 1950 IT specialists knew that testing performed at the very beginning of the project was more resultative. And

Read More

Positive UX – how to make wow effect simple 1

Do you return home if you forget your phone on a table? Can you live at least one day without any gadget or PC? According to the report made by

Read More

Can cyber security culture ensure hacker’s wipeout? 0

Recent successful cyber attacks force to change the attitude to cyber security culture that is closely connected with the company’s culture as well. Poor corporate culture evokes not only problems

Read More

5 “must test” in e-commerce project 0

Nowadays e-commerce is an everyday reality. According to the researchers, by 2019 retail e-commerce sales will count 12.8% of worldwide retail purchases, that means over $3.5 trillion. And every day

Read More

Security Testing Tools You Need to Know 0

The statistics of cyber attacks of the recent years shows that hackers broke 1061 blogs and websites in 2015 and 1017 ones in 2016. But when your website is hacked,

Read More

Hacking: Pluses and Minuses 0

Nowadays hacking is rather popular. Some people are engaged in hacking activity because of personal illegal profit, using confidential or personal information for blackmailing or something like this. For others,

Read More

6 Effective Ways to Perform Regression Testing 1

After performing software testing, reporting bugs and their fix regression testing should be executed. Its aim is to find defects of the software after code modifications or the product release.

Read More