fabiochiu/medium-articles huggingface dataset:
Clariter | Proprietary Tools And Advanced Hi-Tech Ecosystems To Enhance The Qalya Suite
Tags: Clariter, Technology, Hi Tech, Quality Assurance, Data Science

TECHNOLOGY TO ENHANCE THE QALYA SUITE

Technology is important, and at Clariter, we see it as the foundation of our daily lives. Without the different technologies we’re constantly relying on, we wouldn’t be able to offer the level of service we pride ourselves on.

Let’s take a look at the main areas where technology helps Qalya deliver great quality work.

A social network to interact with your customers

Our platform is built upon the model of the four convergent social-mobile-cloud-information forces (see Gartner, Nexus of forces). It consists of an operational area (Negotium), a social area (Otium), and a series of collateral tools (mobile app) that allows the members of our community to interact effectively and carry out tasks anywhere and at any place, day or night.

A complete and advanced test management suite

This is our holistic Test Management Suite, where a complete and continuous management of the test cycles takes place. This includes tools to help with test execution — both in manual and automatic modes and for web and mobile platforms, performance tests, bug tracking tools, and service virtualisation tools for the automation of integration tests.

An environment for a deep observation of the customer experience

We have a series of tools that can support the analysis of customer behaviour in their social interactions. This identifies the path (Customer Journey) and their effectiveness, providing valuable information to improve the relationship with end users. Within this channel there are probes and agents who are able to gather valuable behavioural and technical information, where their correlation becomes vital in understanding the phenomena of poor technical quality that impacts on the overall customer experience.

Support for critical decisions made by our customers

Our composite platform, integrated into Clariter’s very own ecosystem, allows decision makers to make the best decisions at the right time. Through a series of powerful tools aiding with semantic analysis, sentiment analysis, clustering, machine learning & AI and a highly-advanced data analysis, our subject matter experts and data scientists are able to draw the maximum value from the data. This translates into rich and precious information assets to support the critical decisions our clients are required to make every day, thanks to our sophisticated and effective predictive models.
Quality Control vs Quality Assurance: Differences, Cooperation, and Risks
By: Sasha Andrieiev
Tags: Quality Software, Qc, QA, Quality Assurance

Quality assurance (QA) and quality control (QC) are two terms that are often used interchangeably. Although similar, there are distinct differences between the two concepts.

Quality Assurance is popularly known as QA Testing, is defined as an activity to ensure that an organization is providing the best possible product or service to customers.

Quality Сontrol popularly abbreviated as QC. It is a Software Engineering process used to ensure quality in a product or a service. It does not deal with the processes used to create a product; rather it examines the quality of the “end products” and the final outcome.

The main difference between QA and QC:

While doing ‘QA’, we define the processes, policies, and strategies, establish standards, develop checklists that need to be used, and followed throughout the life cycle of a project.

While doing QC we follow all those defined processes, standards, and policies that we laid down in QA to make sure that the project is maintaining high quality and the final outcome of the project at least meets the customer’s expectations.

Follow the guide below that explains the differences between quality control and quality management and provides definitions and examples of each.

https://jelvix.com/blog/quality-assurance-vs-quality-control
Quality Assurance in Data Pipelines
By: Travis Cooper
Tags: Data Engineer, Data Pipeline, Data Integrity, Quality Assurance, Data Engineering

Quality Assurance in Data Pipelines

Photo by Zan on Unsplash

A core responsibility of a data engineer is to build data pipelines. The flow of data from one location to another with mutations along the way is a primary focus for any data engineer. However, when you change data, you make people nervous. Even though you are actively changing the data from its raw form into something usable, it doesn’t change the fact that it is no longer the data that was collected. In order to mitigate these fears, it is vital that data engineers build as many data integrity measures into the solution as possible.

Techniques in quality assurance

1. Byte-by-Byte Comparison

A byte-by-byte comparison is performed to confirm the integrity of the data. A byte-by-byte comparison involves the following:

Ingest the source data, transform it, and load it into the target destination Read the data in the target destination, reverse the transformations, and compare it byte-by-byte to the original source

While a byte-by-byte comparison can confirm the integrity of the data, it is a very expensive operation with respect to time and resources. It also adds an added complexity to the development work as you need to, not only develop the transformations, but also the logic to reverse those transformations. However, it can be executed along side the regular ingestion process to ensure data integrity.

Use Case: This can be used in most pipelines given it transforms the data and reverses the transformations to ensure validity.
What is automated testing?
By: Devy Azkia
Tags: Automated Test, What Is Automated Test, Automated Testing, Quality Assurance, Testers

Hi,

I will share a little story behind the automated test, what is actually the automated test, and how to automate the test? This article is about basic knowledge of QA and automation test.

First, we need to know clearly “what is software testing?” software testing is a process to test the application (mobile or web) to make sure that the application works as it should. the other definition about software testing I found from here (ibm.com)

Software testing is the process of evaluating and verifying that a software product or application does what it is supposed to do. The benefits of testing include preventing bugs, reducing development costs and improving performance. — source: www.ibm.com

That’s the software testing definition.

The other thing that we need to know is “Why do we do the test?”, you know we already know, when we deliver a broken application to users, users will be angry, and nobody using our app, and the application will be useless because there’s no any user want to use the broken application, right? — yes —

And How do we do the test in our cycle development? I’ll give you a short story

The illustration for the development process (designed in Canva)

Short story behind the picture above:

The initiator said “I have an idea to make an application for call and video call”

Business Analyst, “Great, I will design it for development, and give it to developer team, and the QA/Testers team” The Developer, “Let’s do it!”

The QA, “Let’s start creating test cases” The Developer, “Hi, The application is ready for test”

The QA, “yup, the test case also ready, I will test it, and give the result to you”



— the initiator give a new fature and the developer also add the feature to the app and QA make the test case for it The QA, “we need to make sure that the existing feature is working well, but the test time execution continuously increase”

the processes will be repeated, and QA needs to ensure that the new features are working well without impacting the existing feature.

Checking the existing feature should be done every new change or new thing added to the app so that It will take a lot of the QA time 😢. How to handle it?

— yes, you’re right. We need something to make the test faster, easy to run repeatedly. We need The Automation Test. okay, let’s start the automated test.
Postman: Data-Driven Testing
By: Deepak Attri
Tags: Testing, Automation Testing, API, Quality Assurance, Postman

In my previous articles on postman we have discussed how to automate rest apis and how to validate JSON schema. In this article we will see how we can use data files to feed test data in our automation scripts.

Postman provide two ways to pass sets of values to use in a collection run.

JSON File CSV File

By selecting a JSON or CSV data file in the Collection Runner, you can test your requests with multiple different values as part of a single run.

1. Passing data using JSON File

Consider a sample JSON which has 3 sets of data. This data we will be passing to a POST request.

Sample JSON

Here id, cargroupName and cargroupDisplayName are the variables that we will be passing to the POST request.

POST Request

To read the JSON data we need to upload a JSON file from the collection runner.

Collection Runner Window

Click on the select file and upload the data file. The Iterations field shows the number of data sets present in the data file. In our case, it is three but we can run the test on the first two data sets by defining the Iterations. The Delay field defines the time in ms between two iterations.

File Uploaded in Collection Runner

You can select the data type file. It has two options

application/json

csv

Click on the preview to see the data that is uploaded.

You may encounter errors when Postman attempts to read your data file during a collection run. If this happens, you can take the following steps.

Ensure your data file is formatted correctly, as either CSV or JSON. Confirm your data file is encoded properly, by opening your data file in a text editor and saving the file in a different format.

After the upload is successful drag the collection or folder from the sidebar to get started.

Test

To fetch the values from JSON file inside test tab use method iterationData

Lets run the tests.

Test Run

If you see our API has run three times. Each time different set of data is picked up.

2. Passing data using CSV File

When using a csv file everything remains the same just the format of the file changes.

sample csv

Preview Window

That is all for this article.

Full projects and more repositories can be found on my github.
Robot Framework: Login Facebook and post message to user’s news feed
By: Chompoonuch Rassameeamornrat
Tags: Experience, Interview, Software Testing, Quality Assurance, Robot Framework

Here are some of the test cases I used:

### Login ###

User is not able to login facebook with invalid credentials and get the correct error messages

User is able to login facebook with valid credential

User is able to login facebook with phone number

User is able to login facebook with Recent logins

### Post message ###

User is able to post message on facebook at home page

User is able to post message on facebook at profile page

User is not able post duplicate message with recently message >> on hold

User is able to post message with effect on facebook

User is able to post message with photo on facebook

User is able to post message with multiple photos on facebook >> on hold

User is able to post message with tag a friend

User is able to post message with feeling

User is able to post message with checking in

User is able to post message on facebook with photo, friend, location, and feeling

User is able to post message with restriction on facebook

User is able to post with chosen menu >> on hold

User is able to post on story >> on hold

Mostly, they are almost the same for posting, just different post action and verify after posting.

There are some on hold test cases that I could not finish them. It took me more than 8 hours to finish the rest of the test cases. Some of them are Pass when running it individually sometimes but when I run all the cases together, some are Fail.
2 ways of growing QA employee for non-QA managers
By: Petro Tarasenko
Tags: Leadership, Growth, Management, Quality Assurance

The problem

One of the top 3 non-financial things that motivate an employee is growth. And growth is one of the most important tasks of a manager. Sometimes the single QA works in a team without a QA leader. So his/her line manager can be a person from another profession, e.g., Product manager, Project manager, Dev manager, RND manager, etc. Working closely with DEV and RND managers, I’ve seen that sometimes it’s challenging for them to define a growth path for a QA, especially if QA doesn’t know how to grow.

Takeaways

This article should help managers in a situation when QA comes and says:

“Some time has passed, but I don’t see myself growing. I feel frustrated because I don’t understand what significant I managed to accomplish” and you as a manager are not ready to answer this question.

or

“I want to have a salary review”, but you as a manager don’t understand how to evaluate if QA grew enough to have a raise.

Before we start

Firstly, I want to agree on some terms to avoid misunderstandings. Let’s agree that by “growth” in the future we will mean an increase in the impact to a project or company by an employee — QA employee in our context. Let’s consider the following example of impacting: During the last six months, QA employee took ownership in writing project documentation (requirements, user stories, etc.). Before that, these types of documentation were usually missing, outdated or incomplete. As a result, now the team saves a significant amount of time by producing fewer bugs and spending less time finding the actual requirements and clarifying them.

Also, I would like to mention that this article will be only dedicated to cases when QA currently meets all your expectations. Otherwise, it will be pretty easy to grow him — give feedback on things that you think he/she should do better.

Prerequisites

It seems that we’re all set. Before we start digging into details of QA growth, I would like to mention few things that you as a manager have to consider before starting this topic:
QA engineers, functional and UI testing
By: Mirek Stanek
Tags: Android App Development, Mobile App Development, Programming, Software Testing, Quality Assurance

Photo by NordWood Themes on Unsplash

QA engineers, functional and UI testing

This is the second in a series of blog posts in which we outline our multiple years’ experience with our Android app testing at Azimo. Most of the principles, goals, and achievements also apply to our iOS app.

Table of content

QA engineers in the team

Let’s recall our original problem described in the first blog post in the series. It wasn’t about missing unit tests in the first place but about the QA team not being available immediately when we needed them. Why then we created hundreds of unit tests instead of hiring a dedicated QA engineer?

Even if we could do this, we wouldn’t be able to keep him or her busy most of the time. Our app was released no often than once a month. It wasn’t only because of limited access to the QA team but also the questionable quality of our code and bugs and almost no process automation.

Unit tests changed this situation. Writing them improved our codebase quality and overall app’s architecture. With the approach “if something is hard to test, maybe it’s a bug,” we modularized our project, broke down colossal classes into simpler ones, introduced dependency injection, and abstracted SDKs away from our app’s logic.

These changes allowed us to take a step forward and open a full-time QA engineer’s role in the mobile development team. Cleaner code meant changes delivered in smaller chunks, which meant fewer bugs. Better modularity and abstractions gave us the possibility of writing functional and UI tests. We could redefine the QA tester role to QA engineer and focus on a new ambitious goal — 2 weeks release train.

Functional / UI testing & automations

The following months of QA engineer’s work were about two things:

Testing the changes coming with new releases,

Automating these processes as much as possible.

One of the goals back then was “80% of QA manual work is automated”. We didn’t want to spend more than one day per week doing manual tests.

Testing tech stack

We built our testing tech stack on top of publicly available tools. We used Espresso as a testing framework and Fastlane for building pipelines and automation. At the beginning, they were more than enough for our needs. Later, when we identified some gaps, we also published some of the open-source projects extending these frameworks:
Journey of a Manual QA into an Automation World
By: Deborah Calderon
Tags: Coding, Test Automation, Software Testing, Quality Assurance, Software Development

Journey of a Manual QA into an Automation World

Tips to help you transition from manual quality assurance to quality engineering and test automation Deborah Calderon Follow Jun 11 · 7 min read

Hi there! My name is Deb, and I’m a Senior Quality Engineer at Slalom Build. If you’ve found your way here you may be experiencing what I was a just a few years back, at a QA crossroads of sorts. See, I had been manually testing web and desktop applications for about three years. The company I worked for was moving from on-premise to a cloud platform, with the goal of continuous delivery. This meant adding test automation to an Azure pipeline.

So, I had two distinct options:

OPTION 1: Take the opportunity and go for it! Learn how to do it all and implement the automation.

OPTION 2: Run scared in the opposite direction because what was coming was overwhelming. I knew zip about automation, programming, cloud, scripting, and oh so much more.

Well guess what, I chose option 1! I stayed and I learned! And I failed. And I learned some more! And I repeated that pattern until I succeeded. Sure, the final result wasn’t perfect, but it worked! And I’ve since grown into succeeding far more than failing. So to help all you manual QAs staring at an automation dilemma, here‘s how I got started in Test Automation.
Software testing risks
By: Serhii Horoshko
Tags: Testing, Management, Quality Assurance, Test, Risk

Introduction

Risk is something that can happen and lead to negative consequences

Interesting point: sometimes we can do nothing with risk or our effects are not enough to eliminate risk from the list. Systemic risks can not be completely excluded, as are often a feature of the process in which we work.

In this video file, you can find a great team-work example with risks analysis in the software development cycle:

example

Not a bug

How to prevent it?

if you are found an issue that may look like a bug, you must continue with these steps:

You must reproduce it View the test task (Story) Bug localization (minimum reproducing steps)

Create a Bug report

With Confluence descriptions link Requirements Client documentation Design (wireframes, mockups) Logs Screenshots/Video

Risk management activities are cyclical, like any other project activities, if you work in iterations. At the same time, if the iterations are long enough, the work cycles associated with risk management can be several.

An algorithm of working with risks can be presented:

detection analysis and prioritization planning monitoring and reporting adjustment findings

Reference
Two simple ways to be more agile and avoid re-work this week.
By: Leon B
Tags: Agile Methodology, Quality Assurance, Agile, Defect Prevention, Agile Development

Original image from pxfuel licensed to use Creative Commons Zero — CC0

Whenever I ask people about their experience working in an agile environment they often tell me about their two-week sprints and retrospectives. While both these are great ingredients for agile teams, I have seen it been touted as “proof” that a team is now “doing agile”.

Agile is not something we do, it is how we do our work. If we are working in an agile manner we focus on outcomes for our clients and respond to change as quickly as possible. To help accomplish this we need to surface possible issues and changes as early as possible.

This week try these two methods to find potential issues early and avoid rework.

1. Story kickoff

Ready to take a new story from the backlog? Gather your team around your desk, read the story and the acceptance criteria and briefly talk through how you intend to solve the problem.

This is an opportunity to identify:

Is this the correct story to work on now?

Is the story still relevant?

Is the necessary detail in the story?

Are the acceptance criteria correct?

Are there any blockers?

Is the story size correct?

This should not take long and if you cannot complete this in less than ten minutes, you probably need more planning and the story is not ready for development.

2. Desk check

Are you done coding and ready to submit your code for review? Before you do that, do a desk check. Gather your team around your desk again and demonstrate the completed story in action.

This is when you check that your work meets the functional and technical criteria.

Are all the acceptance criteria met?

Are all the edge cases covered?

Are there enough automated tests?

Are the non-functional requirements covered?

This should also not take more than ten minutes. If this step takes too long it is potentially an indicator that the story detail or implementation is incorrect.

Final words

These two simple things will help surface problems and changes early and drive defects down. At the same time it has the added benefit that there will be more team collaboration, and what can produce better outcomes than when we work together?
Quality Assurance and Testing — What’s Important for your Software Development Project?
By: Strides Empower Ltd
Tags: Testing, Quality, Software Development, Quality Assurance

At Strides Empower, our primary focus is about developing a product to suit your requirements:

Quality Assurance is an important aspect in ‘Making sure your product is bug-free, matches all the functional requirements and is displayed properly on all devices’ — Strides Empower.

What is Quality Assurance and Why is it essential for your Project?

The main thing that really matters with any software development project is the quality of the final product itself!

-Does it do what you expected it to do?

-Is it usable by your customers and does it do what they would expect it to do?

-Does it work across all platforms and devices?

Our experienced Quality Assurance Team are there to find any glitches and problems before your customers do.

At each stage of the development process a key focus on Quality Assurance is needed to assure your product meets the required standards. It refers to both the external and internal features of the software.

Quality Assurance analyses software reliability to determine the defects — by a defect, we mean ‘anything that does not match the requirements set out by our clients’ explains Galyna, from the Quality Assurance Team at Strides Empower.
Essential Metrics for the QA Process
Tags: QA, Quality Assurance Testing, Quality Assurance

This article will discuss a few essential QA metrics that must be set and observed throughout the process to ascertain its performance.

The Right Questions to Ask

How long will the test take?

How much money does the test require?

What is the level of bug severity?

How many bugs have been resolved?

What is the state of each bug — closed, reopened, postponed?

How much of the software has been tested?

Can tests be completed within the given timeline?

Has the test effort been adequate? Could more tests have been executed in the same time frame?

Absolute QA Testing Metrics

The following QA metrics in software testing are absolute values that can be used to infer other derivative metrics:

Total number of test cases

Number of passed test cases

Number of failed test cases

Number of blocked test cases

Number of identified bugs

Number of accepted bugs

Number of rejected bugs

Number of deferred bugs

Number of critical bugs

Number of determined test hours

Number of actual test hours

Number of bugs detected after release

Needless to say, the entire QA process hinges on the use of a real device cloud. Without real device testing, it is not possible to identify every possible bug a user may encounter. Naturally, undetected bugs cannot be tracked, monitor, or resolved. Moreover, without procuring accurate information on bugs, QA metrics cannot be used to set baselines and measure success, This is true for manual testing and automation testing.

Use BrowserStack’s cloud Selenium grid of 2000+ real browsers and devices to run all requisite tests in real user conditions. Manual testing is also easily accomplished on the BrowserStack cloud. Sign Up for free, choose the requisite device-browser combinations, and start testing.
Manual Testing Best Practices and Tips
Tags: Qa Testing, Quality Assurance, Qa Testers, Manual Tester, Manual Testing

To overcome the demerits of manual testing, following is a list of activities or the best practices that must be adopted by manual testers in order to achieve great results.

· Thoroughly design and document tests: It is important to emphasize more on the design details and documentation using which a tester shall be able to achieve quite measured and accurate results. The idea is to arrive at a consensus, having the test requirements peer reviewed by the team of testers.

· Utilise the bright side of manual testing: Automation may reduce time and total amount of effort invested by manual testers, but it is always advisable to carry out testing manually in order to apply human mind to a specific problem.

· Strike a balance among test activities: Divide time and resources accordingly by establishing well-defined procedure for completing tasks.

· Rank test cases based on different metrics: Always prioritize test cases, finish the high risk tasks first moving on to next consecutive ones. Finally rank the test cases on the basis of importance, impact on quality, risk factor, the frequency of the feature being used etc.

· Allocate a separate budget for testing: A separate budget is allocated to testing activities for a software. Assessing return on investment is one of the important facts in manual testing because a company is definitely spending for some purpose, and the purpose need to be fulfilled.
Software Developers — Never Say No!
By: Joel Nylund
Tags: Product Management, Software Engineering, Software Development, Quality Assurance

I can’t tell you how many meetings I have been in where the software developer tells someone in product or marketing, “No.” It comes in various forms…“That can’t be done,” or, “We tried that already and it didn’t work,” or everybody’s favorite, “Do you have the budget for that?” Sadly, even the younger version of me was guilty of this once or twice.

But saying “no” didn’t build Google, Facebook and Twitter. I recognized early that in today’s world, just about anything is possible. Heck, Elon Musk is trying to colonize Mars for goodness sake, I think we can figure out how to build a batch job that can process one million transactions in an hour. What it takes is reframing the question from, “Can we…?” to “How can we…?”

This then opens the door to a host of questions that look to do what comes so naturally to software developers — solve problems. Questions like:

1. What do you want to achieve? Understanding the desired result from the business perspective is key to actually solving the problem. So often the end result gets lost in the words used to ask the question.

2. What should we not do in order to do this? Everyone loves to talk about priorities. Everyone hates to actually prioritize.

3. How baked does this have to be when we launch? Can we deliver an alpha or a beta? How many 9s? Are customers okay with software where only the happy path works?

4. Would you trade time for features? Can this be delayed one more sprint so we can get more of your features in?

Instead of saying “no,” we need to be better at finding ways to say “yes.” “Wow, cool idea. It might be difficult, but it could really make our product amazing. Let’s figure out how.”

*Note: Just because something is possible doesn’t mean we should do it. Saying no to something that is dangerous, illegal, or envisions reviving the sock puppet from Pets.com is completely legitimate and warranted.
Lightning-Fast Integrations & Preview Perfection [Updates]
By: Brendan Mahony
Tags: QA, Quality Assurance, Design, UX, Product Design

Hi there.

It has been far too long but fear not — I’m back to share something scrumptious. For weeks, we’ve been listening, we’ve been learning, we’ve been loving and now it is time:

Lightning-Fast Integrations . They were bad. Now they are good 😋 Export issues from Toybox into your existing tools in literal seconds.

. They were bad. Now they are 😋 Export issues from Toybox into your existing tools in literal seconds. Preview Perfection. Oh. Pardon? You want to preview screenshots and comments inside the Toybox app without needing the Chrome extension?? Got you bb 💋

Integrate everything

Our old integrations sucked — they were manual-AF and it took forever to export an issue. We went back to the drawing board and now — exporting issues from Toybox is forking-fast.

How does it work? Simple:

Connect Toybox with your existing tools (Jira, Trello, Asana, and Slack). Select where you want Toybox issues to go inside your existing tools and start leaving comments. That’s it — we do the rest. Poof-Magic.

So, for instance — you’re like: “every time I log a bug using Toybox — I want it to be added to this existing Jira issue, tag these 5 teammates, have high priority status, send a Slack message etc…” and it will DO exactly that.

What’s even cooler is Toybox automatically sends over the (annotated) screenshot, your comment, browser data and more. Save yourself some time and get integrated today.

Perfecting the preview

Getting your teammates or clients to download an extension and sign-up to view your feedback ain’t easy. We’ve been there — we get it. So, we went ahead and made your life a breeze with our new in-app previews.

Now you can view comments, screenshots, metadata and more inside the Toybox app. No installs, extensions, or sign-in required. Don’t fret though — if a teammate has a question and wants to reply to your note, they can simply sign-in as a guest and do so — all within the app!

In Conclusion

I want to thank everyone who has given their time and feedback to help us improve Toybox. We’ve got some incredibly exciting things cooking up in the ole kitchen — so keep an eye out.

In the meantime, please DM me via Twitter if you have any ideas or ways we can make Toybox work better for you and your team! Lastly, sign up for our mailing list below to stay up-to-date on all things Toybox :)

👉 Learn How To Supercharge Your Design QA Process Here.👈
Building a World-class Software Quality Team from Scratch
By: Julie Griech
Tags: Engineering Management, Software Testing, Quality Assurance, Tech, Software Development

Building a Team

Once each of the categories becomes filled up with information and ideas, I start to formulate what the testing team will look like and how the team should operate. At this point, I am not considering how many testers will make up the team — I am thinking more along the lines of what do I want to implement, which looks more like a high-level view of what function would need to be filled regardless of how many people fill them.

Example: in order to achieve my planned goals, I very much require the following functions: a) mastery at test planning from vague requirements, b) mastery at ad hoc and exploratory testing, c) highly-skilled automator, and d) excellent at pairing with developers to understand features with no requirements.

These functions and skills take shape not only based on what we want to achieve, but also based on some of the pain points that may have caused failure to deliver in the past. A practical application of a very detailed function is that you may need a team member who is very adaptable when things change given the fact that the organization makes constant changes on the fly for every new feature.

The Secret Sauce

Regardless of what specialized skills are needed, there are some basic must have attributes for testing team members. These are the common traits that individuals have that make them invaluable and successfully extensible to most any task.

The common traits are: a) a deep understanding of SDLC, b) superb communication and writing skills, c) mastery at creating test cases, test plans, and defects, d) highly organized, and e) they must be a team player.

The combination of the specialized skills and the must have attributes are the magic that make up an outstanding testing team.
Quality in Projects
By: Kristina Kushner
Tags: Project Management, Quality, Quality Assurance, Agile, Projects

What is quality and how to implement it into the projects we manage? How to ensure our projects are of quality? Do you know how to measure it?

Hey Crizpers, today let’s look into the definition of quality and let’s try to apply it to our projects. How could we take care of quality in projects and to make sure we are compliant with the certain quality standards? And are there any multi-applicable standards we should consider?

What is Quality

First of all, let’s see, what quality is. According to Wiki:

Quality is a perceptual, conditional, and somewhat subjective attribute and may be understood differently by different people.

This is a general definition, as I am trying not to addict to any specific area or industry. The main point here is that the meaning of quality is different for people and we do not have a common understanding of quality with others by default.

We cannot just say our project or product is cool and amazing. The reasonable question would be: Cool and amazing against what? How do we know it is amazing?

Thus, to ensure whether the product is great or not, there should be certain measurable criteria that we are estimating against to.

Quality is a confirmation we are aligned with the certain standards or surpassing them. For instance, our website is loading less than 0.1 seconds which is 50% faster than websites of our competitors; we are on the latest version of PHP; our product security measures corresponds to the global standards, etc. We need to use some guide or beacon that is widely known or at least set up internally to confirm our level of Quality.
Steps should be executed for performing Computer System Validation
By: Bahgwat Sonwane
Tags: FDA, Data Integrity, Csv, Quality Assurance, Validation

In Earlier post we understand what is Computer System Validation, Why CSV Required, Purpose of CSV & Benefits of CSV.

Now in this article we are going to understand steps which should be executed during computer system Validation activity. These steps will helpful to understand how CSV will be performed.

Each & every steps having its own importance. So, Never miss any steps while performing validation activity.

Steps which never missed in computer system validation.

GxP Assessment & System Categorization

System Level Risk Assessment

User Requirement Specifications (URS)

Functional Specifications (FS)

Design Specification (DS)

Project Validation Plan (PVP)

Configuration Specification (CS)

Requirement Traceability Matrix (RTM)

Software Code Review

Qualification Protocol (IQ/OQ/PQ/IFQP)

Generate Test Script

Qualification Report (IQ/OQ/PQ/IFQP)

Discrepancy Form (DS)

Discrepancy Log ( DL)

Validation Summary Report (VSR)

System Release Certificate (SRC)

Signature Log (SIL)

GAP Assessment

Screen Print Attachment

Validation Document Log (VDL)

Validation Master Plan

System Deliverable Matrix

Impact Assessment

CSV Document Preparation, Review & Approval Matrix

Project Change Management Form

Project Change Management Log

All these above steps are need to be performed during successful computer system validation. Let’s break down each part a little bit further in next article.

Download our Free Data Integrity App to access more related content.

Across the internet, there are millions of resources are available provide information about almost everything.

Here all useful Pharma IT Compliance & Inspection preparation information is available in your hands for your ready reference.

We recommended you this “Data Integrity” App which contains most important Pharma IT Compliance tricks & techniques which help you to understand

Current Regulatory Agencies thinking on Data Integrity.

Importance of Mock Inspection & its tricks and techniques how to conduct.

Checklist for Inspection

Best Practices for CSV.

Useful Resources & References

So, let’s try this Free “Data Integrity” app & stay updated in world of Pharma IT compliance.

Team Innovative Appz
Getting started in Data-Driven testing with Katalon
Tags: Testing, Automation Testing, Dipostarfinance, Quality Assurance, Data Driven

1. Create Test Case and add Object

Firstly we need to create a new Test Case i.e: User Login, and add some object locator either by record using Katalon’s own recorder or manually add an object locator using available object properties

Object Repository

2. Create a Local Variable

The next thing to do is we need to add a local variable in the User Login test case to bind with test data in the test suite later on

Local Variable

3. Add Steps in Test Case

After that, we create a step in the test case, for example in the following steps:

Open a browser and navigate to the URL Set text on the email field Set text on the password field Click the login button Lastly, verify the text in the username title, in this example we use Katalon Verify Element or you can swap it with an assert statement.

Note that all the “Input” shall be mapped with the variable that we’ve been defined before.

User Login Test Case

4. Prepare the test data in excel doc

For the test data we have to fill the row with a column header, and also a set of credential that will be used in the data-driven sign-in and verification process

Test Data

5. Attach Test Data in Katalon

After we have a test data, open our Katalon, create a new project and attach the test data to it, and the row data/record will be displayed in File’s Information

Attached Test Data

6. Create a Test Suite

When the test case is done, the next step is to create a new Test Suite to do a data binding and used it as a test case container

Test Suite

After done creating a new test suite, bind the variable in the test case with the test suite, set Data Iteration to “All” to run all the available records in test data.

Binding Test Data

7. Run the Test Suite

Finally, we run the test suite and it will do a complete run on the test case multiple times based on how many row/records that available in the test data as shown below

Test Run Result

Conclusion

Testing a case with a huge amount of test-data, let’s say 1.000 records of data to verify the expected result would take quite some time when test it manually, there is also a possibility of a human error in it, by using a data-driven method it will reduce those obstacles and minimize the effort when the test data is increasing over time, due to we will no longer need to modify the script much or even at all.

By using the Katalon framework to start creating data-driven testing, it is fairly straightforward hence already familiar with the concept, from there the complexity will vary to the case requirement and your approach on how to automate a case using the data-driven method.

The shown above concept itself will be able to translate quite the same when using other tools/frameworks example such as TestProject, Cypress, or Selenium in respective IDE, except that it might require to write more code and importing necessary framework or library when using Selenium for example.

Thanks for reading and Best of Luck!
Deadlines, nightmares and how to make it less painful….
Tags: Development, QA, Software Development, Quality Assurance, Software Engineering

|how to overcome the nightmare and make it an achieved dream.

When we talk about deadlines, we are talking about a full commitment not only for the IT crew but also for all the other teams in the company(marketing, business, press, etc)

So why is always so difficult to find a fit date to deliver?

When we talk about a fixed released or delivery date we are talking about a scenario where every single team involved in such project is at a confident level to be able to face any difficulties that. might come ahead.

One tiny-big problem on tech, is estimations done by mostly Business and marketing team without involving much of the development team or given second thought to the work in hand that would have to be done to be able to meet such estimations. Hence is part of the life cycle to speed up more than once to meet certain deadlines.

Let’s for instance talk from the marketing side, if we are talking about a new product they have to plan everything around it regarding exposure, newsletter, advertising, planing, consumer reach etc…

When wrong estimations are made, deadlines seem tight, I’ve seen the development Department pushing the extra mile to be able to deliver at least something so the entire marketing investment does not go in vain, just due poor Communication and involvement in the corresponding teams.

But this is something normal.

In a perfect scenario such negotiations should always included someone from the engineering team, that will be capable to give a more realistic estimation and/or more options that could even increase the value and quality of what needs to be done.

Is not witchcraft, is just simple a sharing and communicative culture will solve most of todays problem.

That’s at least how this QA sees it.

Also check out:

Getting QA back in the Game

What’s a QA Architect?
Internet of Things Security with Arrows Group
Tags: Security, Cybersecurity, Software Testing, Quality Assurance

Written by: Travis Hatridge

At the end of March, our managing director of cybersecurity services, Justin Leavenworth, took part in a webinar discussing the rise of IoT and how to combat cyber risks. For those not so familiar with the subject of the Internet of Things (IoT), these networked devices are predicted to change not only our personal lives but also our professional lives.

The most commonly associated IoT devices are things like smart refrigerators, homes assistants like Alex or Echo, and smart lighting like the Philips Hue lights. Outside of the consumer electronics side, IoT has the potential to revolutionize manufacturing, agriculture, and infrastructure but turning previously dumb machinery into smart machinery by connecting them to networks. This means that there is more data available for organisations to optimise processing and the ability to control critical functions remotely. This is one of the areas of IoT that is at risk of cybercrime.

This webinar included a panel of cybersecurity experts and discussed IoT from the business and technical perspectives, as well as looked at the dangers of IoT and what they mean for businesses and consumers.
For Me, It Is The Hustle That Stands Out!
Tags: Inside Invideo, Video Creation Tool, Quality Assurance, Engineering, Invideo Hiring

For Me, It Is The Hustle That Stands Out! InVideo Follow Apr 6 · 2 min read

Meet our QA Engineer, Saniya Shaikh. A hustler, she believes that it is the learning opportunities here that help her grow and be better at her job!

How did you come across InVideo?

My ex-colleague referred me to InVideo, and my previous company Republic TV was a client of InVideo.

What was your interview experience like?

Quick and Fast. I had two rounds of interviews. The first round was with Pankit which was majorly screening and involved a few technical questions. And the second round was purely technical and skill-based with Ronak.

Why InVideo?

I like responsibilities and opportunities. So I always believe startups are the best place to learn and grow personally and professionally. Being in InVideo for over a year, I like the flexibility and versatility at work and how my role involves being responsible for product quality.

Finally, what’s one moment/incident that stands out in your time at InVideo?

I miss the end-of-month celebrations! The yummy Maharashtrian lunch by Aunty, Chai breaks with colleagues, Salsa workshops at We Work. Out of all the moments, what really stands out is the hustle and coffee during the late-night releases and how we used to celebrate the success after every major release. The templates page release was a memorable one.
The Importance of QA Testing in Business
Tags: Testing, Technology, Software Development, Quality Assurance

Photo by NESA by Makers on Unsplash

FREMONT, CA: Quality Assurance (QA) stands as a quintessential part of a business process. QA strategies provide product developers and other software experts with methods to review the product and check for defects and errors in the code. With the full-fledged QA protocols, testers and quality analysts obtain broader insights into product standards, service grade management, and more. The latest upgraded QA software testing program sophisticates the quality check processes and drives outcome accuracy to a vast extent. Here’s more to why QA becomes a critical aspect of the business. Read on!

• Driving cost efficiency

Technically well-designed quality assurance procedures serve as a cost-effective strategy to overcome almost every issue related the product quality. Costing least, and demanding minimum expertise and time, advanced QA software solution allows the developers to test the output remotely. QA management software testing program eliminates the need for onboarding highly skilled experienced and expensive testing professionals.

• Mitigating risks and hardships

As this fully digital QA tool automates the testing workflow and requires minimum human assistance, enterprises need not have to worry about the strict deadlines as the software model executes test routines, with ultra-fast processing capabilities. Features such as active unit and integrated testing add to the benefits offered.

• Backing testers with software flexibility

Tech-driven QA testing mechanisms support software compliance, which further helps the software development team to deploy and implement the software testing program efficiently. Read More…

check out: Overcoming Barriers in Key Infrastructure Assets Management