Level Up Your Quality with a Maturity Model

 Quality Maturity Model

This framework helps IT organizations improve quality by providing a roadmap for process enhancement. 

It enables systematic quality management, leading to high-quality products, customer satisfaction and competitive advantage...

QMM framework that helps to achieve better business outcomes. 

It assesses current quality levels, identifies gaps, and provides a roadmap for improvement, leading to efficiency and cost reduction.

A Quality Maturity Model aids analysts in pinpointing improvement areas, achieving process consistency, enhancing efficiency, and cutting costs for heightened product or service quality.

The Quality Maturity Model (QMM) assesses organizations' quality maturity in five stages: Initial (no defined processes), Managed (basic practices), Defined (well-documented processes integrated into culture), Quantitatively Managed (data-driven decision-making), and Optimizing (continuous improvement focus).

Steps to implement the Quality Maturity Model:

1. **Assess Current Quality**: Evaluate existing processes and tools.

2. **Set Quality Goals**: Define clear objectives and metrics.

3. **Plan for Improvement**: Create a roadmap with prioritized actions.

4. **Implement and Monitor**: Execute changes, track progress, and adjust.

5. **Continuously Improve**: Regularly review, learn, and enhance.

Remember, effective communication and engagement are key at every stage.

How to score runs in a developer's pitch?

When communicating or informing a developer that a bug is a bug, it's essential to be clear, precise, and provide sufficient information to help them understand the issue. Here are some steps to effectively communicate a bug to a developer;

Confirm the Bug: Double-check that what you're experiencing is indeed a bug and not an intended feature.

Share System Info: Mention your operating system, browser, or any relevant details about your setup.

Describe the Problem: Clearly explain what the bug is and how it affects the system.

Explain Expected Result: Describe what you were expecting to happen instead.

Show How to Reproduce: Provide step-by-step instructions on how to make the bug happen again.

Attach Screenshots or Logs: If possible, show visuals or error messages related to the bug.

Importance: Indicate how much the bug impacts the system's performance or functionality.

Follow Up: Check if the bug gets fixed and provide feedback if needed.

Be Friendly: Use a polite tone when communicating the issue.

Stay Available: Be ready to answer any questions the developer may have.

---

By following these simple steps, you can help the developer understand and address the bug more effectively.

---

 

ProTesting

In software testing, a dispute, complaint or objection can arise in any situations. Here is a general approach to handle such events;

1. Understand the problem: Get all the details about the conflict, complaint or objection in software testing.

2. Talk to the concerned person/group: Have a conversation with the people involved to better understand their perspective and concern.

3. Investigate the issue: Look into the problem thoroughly. Review test plans, cases, and other relevant information to find out what went wrong.

4. Find a solution together: Collaborate with the stakeholder to come up with possible solutions or compromises that address their concern.

5. Review the testing process: Check if the testing was done according to the established standards and procedures. Look for any mistakes or deviations.

6. Involve higher authorities (if needed): If the issue can not be resolved through discussion, seek help from management or higher-level authorities or friends from your organization.

7. Learn & improve: Reflect on the situation and see if there are any lessons to be learned. Make essential improvements to prevent similar issues in the future.

Finally ProTesting is how you solve the problems and be a professional in your career...

Remember, adapt these steps as needed to fit the specific circumstances you're facing...

I See You

Product instructions in the form of user documentation (or) handbook are a valuable element to any product. It is vital to assess if this content is usable and has a positive impact on a user’s experience.

When instructional aides are too difficult to understand, the result can be worse than a product. By putting yourself in a user’s shoes and statistics, you’ll be able to assess if the instructional content meets the needs of the anticipated audience.

Try to have a document for each functional portion [Functional Break-up Document{FBD}], so that it might help you one day...

#SoftwareTesting 

#QA 

#TestAutomation 

#Documentation   

THE

Testing HemispherE

Software Testing is a Globe, where you have 2 hemispheres.

One is Manual and the other is Automation. Most companies have both automated and manual testing efforts together. You might disagree but the fact is "there needs to be balanced Automated and Manual test approach for a process/product triumph."

High-quality productivity comes in when your manual test engineers have created a complete set of test cases that have immense traceability and test coverage, and then your automation engineers have automated your smoke & regression test cases.

Software Testing || QA

Test Automation || Product Testing

Continuous Integration || Regression Testing

WEST

WEb Service & Testing

Techniques such as White, Grey and Black Box testing relates to traditional systems, which directly sync-up into Web Services deployments.

However, the following uniqueness of a Web Services deployments introduce exclusive testing challenges:

*) Web Services are fundamentally distributed and are platform and language doubter.
*) Web Services can be a sequence with dependencies on the other 3rd party Web Services that can change without notice.
*) Web Services ownership is shared across various stakeholders.

Software Testing || QA

Web Services || AWS

Load Anyway on Google Chrome

Where I can see the Load Anyway concept/theme in Google Chrome???
Here It Is...

   

In general, the https will be in green [indicating the site is secured] but after allowing the unsecured data, it automates to red, with a strike through the header to indicate that it has loaded insecure content [as in the second image].

Mini Magick's Magic

~Happy Watir Day~

While running a "Watir" programs; if you get "ERROR: While executing gem ... (Errno::EINVAL) Invalid argument - C:/Ruby200/lib/ruby/gems/2.0.0/gems/mini_magick-3.6.0/tes t/files/special! "chars'.gif"...

Solution: Its so simple; do the following steps. It works...
i) gem uninstall mini_magick
ii) gem install mini_magick -v 3.5.0

Cc:

Customer Connection [Cc:]

1) Inform Your Client [IYC]

We need to spend time to educate our client about the current project. Technology is not a top secret any longer. We are living in an open-source environment, so always unlock the so-called “Top Secret”.

2) Recognize Your Client [RYC]

Spend time to speak to your client on their area of interest. We could chat about soccer/cricket, travel, food, uniqueness of the place etc., anything that has crossroads with your interest. These connections will bring in faith.

3) Be Crystal Clear [BCc:]

Yes, all the Apps do have traffic jams. It’s not about clearing-up the traffic jams; it’s all about sorting out the issues at the initial level. Be so transparent to your client on the project concern and known threats.

4) Nod Your Head: “YES” [NYHY]

It’s tricky, still we need to adopt it. Willingness to agree the challenges and new R&D work could let you in superior books of your client. It’s not only a project delivery, but for our own knowledge too. Make sure it’s not happening very often and be clear to draw a line between extended work and exploited effort.

5) Nod Your Head: “NO” [NYHN]

We need to take the time to understand why our client is asking us to do this; let them know our reasons against it, and try to find any further solutions together. Client is GOD, but they are “Always not Right”. Help them to make balanced judgment (if needed). Don’t agree to the things, which could go awful. Better not to fight with fire [than] struggle with an alarming flag.

6) Gently Observe [GO]

Let it be phone call, mail or chat; Listen to your client patiently. Most of the time people find it difficult to communicate what they feel. They will be in search of words and trying hard to put the things on your table. So don't end with any ideas until the client feels that they are comfortable on what they wanted to communicate fully. Listening patiently might be tough, but it will bring in immense profit.

7) Boost-Up Belief [BUB]

Best way to increase your client’s faith is to keep-on focused on your deliverables. When we deliver what we say and when we say we will deliver it, we build our trustworthiness and enhance our rapport. The trust the client gives us increases, and will help us when we insist “this task will take two days” for instance, when they imagine it’s just a easy tweak and shouldn't take more than a couple of hours. The most significant thing is letting them know that we are part of the team; we are both on the identical boat, planning the same goals. Once your client recognizes that their failure are also your failures, and their success are your achievements as well and the other way around, then you’ll be a step further in expanding their trust.

8) Throw-Away Compliments [TAC]

Make sure you send occasional greetings to your clients. New Year, Christmas, B'day or any grand day to send greetings would be a pleasant way of being sociable.

9) Enjoy Your Effort [EYE]

Knowing the client relationship is part of your job. Your efforts are forever enjoyable.

10) Keep Distance [KD]

Always be clear on your roles and responsibilities. We need to be careful in keeping our distance so we can persist to provide valued advice and knowledge.

BACB = 2 – Legacy Application

In information technology, legacy applications and data are those that have been inherited from languages, platforms, and techniques earlier than current technology.
Most enterprises that use computers have legacy applications and databases that serve critical business needs.
Typically, the challenge is to keep the legacy application running while converting it to newer, more efficient code that makes use of new technology and programmer skills.
In the past, much programming has been written for specific manufacturers' operating systems. Currently, many companies are migrating their legacy applications to new programming languages and operating systems that follow open or standard programming interfaces.
Theoretically, this will make it easier in the future to update applications without having to rewrite them entirely.

Courtesy: some site when I searched on this term.

Remote Testers

There is an aged-old saying like “Testers should be divided from Dev/BA team & they should work independently”.
The above statement is linked to the bizarre style of testing, as what is the role of testers and what testers should perform.
If you are cautious on the thought that your testing team must be isolated from other teams, then there is a better possibility that you and your team will achieve more testing; (since you are free from expressing your own test ideas without other’s suggestion/feeds).

BACB = 0 – Intro

Making the first move for “Being a Cordial Bugzy” ["BACB"]

Meaning for “Being a Cordial Bugzy” : “Im here to Share my Info related to Software Technology”

ABCDE of a Software Test Engineer

“ABCDE” of a Good Tester’s Quality;

• You Agree to the work/attend official calls apart from your office timings/working days.
• You are always Brisk on explaining the defects on tracking system.
• You are Conscious of your application’s business view and testing life cycle.
• You are Delighted doing multi-application testing.
• You are Ecstatic of your role in your project.

BACB = 1 – Comments on MS word

Q => How to add “Comments" on ‘Microsoft Office Word Document’?
A => Under the “Review tab”, you have the option for adding/deleting options for the comments.

Tip => For better understanding on versions of comments, you can have the access of the following;
“Change Tracking Options” under ‘Track Changes’ and “Reviewing Pane”.

Rubber Stamping Ideas in Software Testing

Rubber Stamping in Software Testing >> Re-Usability/Framework Usability in Automation.

1. The test scripts will be less expensive due to the better rubber stamping.
2. Modification to the test scripts won’t affect the test data.
3. Healthier rubber-stamping is attained only when the scripts are organized properly.
4. Open to any Test Tool.
5. Test cases can be performed with ample number of data when rubber stamping is fittingly used.
6. Simple script management.
7. Independent of Application under test and same script works for every level of testing.
8. Testing can be planned with/without AUT (Application Under Test).
9. It offers notable (Depends on type of framework).
10. Range of test scenarios can be executed by changing the test data in the external data (as most of us use xls file).

Spoofing For Testing

Hope you guys would have heard about the "Email Spoofing"....

If not, it’s nothing but to steal other’s personal information. When you open (or) view the spoofed email, you expose yourself to hackers who desire to access your inbox and personal records. Emails are spoofed and sent with an intention to mislead. It is considered an illegal activity.

So, what can spoof do for software testing?
Some spoofing points are as follows;
>> Uploading HTML/Script files in your application.
>> URL Injection.
>> Checking the expired Authentication Tokens.
>> Verifying the Bookmarked Web pages (in your application) with other logins.
>> Cookie Decryption.

There are bunch of points apart from the above. Make the best use of the spoofing & phishing techniques while doing software testing....

Triple T

Finishing point of task is complex to report; as there is no specific time period to test the application, there is just completion time specified (module end/release date).

If some specified time is likely given from managers, there could be a few minor functional items omitted at that point of time taking in explicit major functionalities alone in the account.

Overall test execution will be specified in days but generally in a module base testing, it will be mentioned only in hours; as it’s easy to track-in. In some cases, the time specified for a module in job card will be adjustable.

If handful functionalities are there then it can be easily analyzed and tested well before the scheduled time. Task estimate is always a recurrence procedure.

In our test estimation, time consumption happens (double the time from the initial estimation) because of slippages (build delays & iterations) from incorrect estimation.

Apart from meetings, a project task is generally estimated half a day (or) a day (or) in hours. I can observe that we all have a pattern to manage our teams but strategy is identical.

Question: So what's "Triple T" ???
Answer: Triple T >>> "Task Taken Time"...

Testing always depends on Task and Time to make a software look like a Triplet...

CT scan

Ever since our apps are on the cloud, we need to think testing as the same.

Functional & Performance Testing Tool, Defect Tracking & Test Management Tool, Capture & Playback Tool, Regression Testing & Database Testing Tool will be provided by service in TaaS.

TaaS means operating Software Testing with a group of people and tools.

1) Main drawback in general cloud service is the security of the data.
2) Another drawback is when some data disaster happens; revival of data will be complicated.

In some testing services, the Cloud Testing package offers the opportunity to access Test Tools with the Test Environments from anywhere around the world.

[CT scan - Cloud Testing scan]
[TaaS - Testing as a Service ]

Testing the Tester’s Pulse!

Height of frustration when our “Project Manager”/ “Team Lead” ask the following statements.

1. Are you sure, you have tested and verified the functionality?

2. Speed up and complete the sanity/regression testing soon as we need to push the latest code into the production instance.

3. It’s just a ‘Change Request’, it will take an hour to test those changes.

4. Guarantee me that, there are no bugs in this tested build.

5. I have a Client Demo within an hour/today, so just have the tasks done. Need this to be in live within the specified time-frame.

6. Are you bored on testing this application repeatedly?

7. Come on/ Plan for Saturday, Sunday or Holidays to test the application.

8. I didn’t have time to read your bug report. Just examine by yourself and close it.

9. Close all the bugs today itself and give an ideal defect report which provides a clear info. (Instead of using the term Testing.)

10. Kindly communicate with developer team and plan accordingly for all the bugs you have posted on Defect reporting tool.

Error Code: (1719) Windows Installer

Yesterday, I tried to plugging-in my USB port with (my mobile with CPU) but there was an access error. Error Code: 1719 [The Windows Installer service could not be accessed.]

If you are getting this error, try the following; as it helped for me.

Sometimes, if the Installer service is disabled, you will get this error. You can turn it on by going to Start, then Run and typing in "Services.msc".

Then scroll down to Windows Installer and double-click on it. Set the Startup Type to "Manual" and click Start to start the service.

Try now... Hopefully your issue is resolved.

You can also start the service by going to Start, Run and type in net start MSIServer into the Run box.