All About Testing

All About Testing Artificial Intelligence Design and Technology

This is the place for all be it Developers or QA...
The platform to discuss common issues we face while testing a site...
We can help people by sharing our experience... may be that will help them resolving the issues
Any topic...
from the template for test case, use case... etc to Testing tools

✨ Introducing AIDT Innovations – Powering Digital Innovation ✨We’re proud to introduce AIDT Innovations, a UAE-based tec...
19/01/2026

✨ Introducing AIDT Innovations – Powering Digital Innovation ✨
We’re proud to introduce AIDT Innovations, a UAE-based technology company founded in 2025 with a clear mission —
to help businesses innovate, scale, and succeed in the digital world.
With 20+ years of combined industry experience, our expert team partners with startups, growing enterprises, and global organizations to deliver intelligent, secure, and scalable digital solutions.
At AIDT Innovations, we believe true innovation happens when Technology meets Creativity.
That’s why every solution we build is designed to be powerful, user-friendly, and future-ready.

aidtinnovations.com

19/07/2017

These days we use Agile Methodology for the software development.
What is Agile.
Agile means ‘ability to move quickly and easily’ and responding swiftly to change – this is a key aspect of Agile software development as well.
This methodology is very flexible and adjustable and can adapt to the project needs.
The style of management in Agile model is not centralized. It is distributed among the team members.
This is how Agile methodology works faster and make complicated process easier.

08/05/2013

What is Boundary value analysis in software testing?
Boundary value analysis and equivalence partitioning both are test case design strategies in black box testing.
BVA Black Box testing technique believes and extends the concept that the density of defect is more towards the boundaries.
This is done due to the following reasons

a) Usually the programmers are not able to decide whether they have to use

25/08/2012

Goals for the Facebook Connect integration are:
- New User Sign Up without needing to create a site-specific password (email address needed)
- Ability for existing users to link with their Facebook account
- 1:1 mapping between accounts on your site and Facebook accounts
- Single sign-on experience

Few Test cases will be in such a way:
Sign Up should fail if the user denies permission to the app (category: sign up)

Since we need access to an email address, Sign Up should fail if the user provides publish permission but denies email permission (category: sign up)

If the user provides an email address that already exists in your system, fail Sign Up.

Attempting to Sign Up with a Facebook account that's already linked and authorized should result in the Sign In experience (category: sign up, sign in)

Attempting to Sign In with a Facebook account that the app hasn't seen before should lead to the Sign Up experience, i.e. create a new account (category: sign up, sign in)

Like the page to see more of these Test cases and Tips and Tricks....

06/07/2012

Tip of the day....

Three types of quality attributes:
1. Product Operations
2. Product Revision
3. Product Transition

Quality factors are mapping its attributes:
Product Operations:
• Correctness: does it do what I want?
• Reliability: does it do accurately all the time?
• Efficiency: will it run on my machine as well as it can?
• Integrity: is it secure?
• Usability: can I run it?
Product Revision:
• Maintainability: can I fix it?
• Flexibility: can I change it?
• Testability: can I test it?
Product Transition:
• Portability: will I be able to use on another machine?
• Reusability: will I be able to reuse some of the software?
• Interoperability: will I be able to interface it with another machine?

04/07/2012

Hello All,

This page is all about testing or testers. Request you all to please write a short introduction of yours so that we all can know each other.... This introduction can include your skills, what you are working on etc...

29/06/2012

Few areas that should probably always be covered in your functional testing strategy of Mobile Application:

Sign-up & Login: This may seem like a no-brainer, but if users
cannot easily access your application, your efforts will have been
wasted. If your app or mobile site requires password and username
(not recommended), pay close attention to the fields and make sure
that it’s easy for users to enter their information.
• Menu Options: Often times, menu options can be difficult to
access and decipher. Make sure that menu items like Help, About,
etc. are easy to find and navigate.
• Keys: Any problems related to scrolling, text selection, the back
button, etc. are bound to lead to trouble, so make sure your key
functionality is clear and consistent. Also, be sure to cross-check if
your app will run with a keyboard and/or touch-screen.
• Data Handling: An important consideration for all mobile apps (but
for games in particular) is data handling. Does your mobile app
store saved information properly? What about data deletion – or
worse – unintended data deletion? Make sure to include this in your
testing scope.
• Connection Speed / Carrier: With the iPhone now running on
Verizon, Sprint and others, testing on only one carrier is no longer
an option. Make sure that your most basic app tests include some
of the most popular (and likely) carriers, as performance can vary
greatly from one carrier to another.
• Operating System: Like carriers, the mobile operating system
running your app will have a huge impact on its relative performance.
• Screen Size: While this applies mainly to tablets, screen size
Discrepancies should be a top consideration while testing your
mobile app. For instance, how much should users have to scroll
from left-to-right or top-to-bottom, if at all?
• Interruptions: How does your mobile app behave when the
device battery is at full strength, medium strength and low
strength?
• Error Messages: Your error messages should be clear, concise
and actionable.

28/06/2012

Software has defects because of the following reasons:

* Incorrect requirements
* Inadequate Testing
* Wrong design
* Poor coding
* Complex business logic
* Complex technology
* Work pressure
* Frequently changing requirements.
* miscommunication

And?

Address

Abu Dhabi

Website

Alerts

Be the first to know and let us send you an email when All About Testing posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Share