Testing doesn't stop
at the desktop app.

Forms are part of any website used for receiving information from users and to interact with them. Check:

• All the validations on each field.
• Default values of the fields.
• Wrong inputs to the fields in the forms.

Cookies are small files stored on a user's computer, holding data specific to a particular client and website, accessed by the web server or the client.

• Test by enabling or disabling cookies in a browser.
• Test if cookies are encrypted before being written to the user's machine.
• Test if cookies are deleted when they are not needed anymore.

• Checking for syntax errors.
• Check if the site is crawlable by different search engines.
• Readable color scheme and fonts.
• Standards compliance (e.g. W3C and ISO).

• Data validity: test if any errors are shown while executing queries.
• Data integrity: check for errors while editing, deleting, modifying data.
• Check response time of queries; confirm queries execute correctly.
• Check retrieved data is shown accurately in the web application.

Vital for web applications that store sensitive customer information like credit cards, IDs, and passwords.

• Unauthorized access to secure pages should not be permitted.
• Restricted files should not be downloadable without appropriate access.
• Sessions are automatically killed after prolonged inactivity.
• SSL certificates redirect the site to encrypted SSL pages.

Ensures your site works under all loads.

• Response times at different connection speeds.
• Load test — behavior under normal and peak loads.
• Stress test — find the break point beyond normal load at peak time.
• Test how the site recovers after a crash caused by peak load.

Ensures the app performs acceptably under certain performance requirements, such as access by a huge number of users or the removal of a key infrastructure part like a database server.

• Performs correctly under peak, average, minimum user loads.
• Client-server config gives optimum performance.
• Identify application/infrastructure bottlenecks.
• Battery life supports the app under projected load.
• Performance holds when switching WIFI ↔ 3G/4G/5G.
• Battery consumption, memory leaks, GPS/camera use stay within guidelines.

Ensures the application's data and networking security requirements are met as per guidelines.

• Withstands brute force attacks (automated trial-and-error to guess a username/password/credit-card number).
• No sensitive content/functionality without proper authentication.
• Strong password protection; no session expiration gaps.
• Prevents SQL injection; validates certificates (certificate pinning).
• Protects against denial-of-service, buffer overflows, malicious client-side and runtime injections.
• Regular audits for data protection analysis.

Performed to have a quick and easy-to-use app rather than a slow, feature- heavy but difficult one. Goal: easy-to-use, intuitive, similar to widely-used industry-accepted interfaces.

• Buttons sized for big fingers, placed consistently, natural/consistent icons.
• Same-function buttons share the same color.
• Tap zoom-in/zoom-out enabled; keyboard input minimized appropriately.
• Undo/back available within an acceptable duration.
• Contextual menus not overloaded; text short, clear, readable font size.
• App re-opens in the same state; strings localize when translation is available.

Ensures the app is tested across all devices — since mobile devices differ in size, resolution, screen, version, and hardware — so it works as desired everywhere.

• UI matches the device's screen size — no partially invisible or inaccessible text/controls.
• Text is readable for all users.
• Call/alarm functionality works while the app runs — app minimizes/suspends during a call, resumes after.