Task -2 Manual Testing: Testing a New Mobile App for Different User Types.
Photo by Joanna Kosinska on Unsplash
Q2.
Any registration page has several functional and non-functional features that need to be tested. Below are the functional & non-functional test cases for a registration page . This list comprises a variety of test scenarios for the registration page, including both positive and negative cases, various security test cases, and UI test cases.
Feature to be Tested :
First name :
1.Check if the first name is mandatory.
2. Check if the first name field uses only alphabets.
3. Test if the field shows error message for numbers and special characters entry.
4. Check if the field shows an error message when left blank.
Last Name:
1. Check if the last name is mandatory.
2. Check if the last name field uses only alphabets.
3. Test if the field shows error message for numbers and special characters entry.
4. Check if the field shows an error message when left blank.
Email address:
1. Check for valid email address format.
2. Check for invalid email address format.
3. Test if the email address shows an error message when left blank.
4. Check if the field is case sensitive.
5. Test the field with leading/trailing spaces and for its maximum length.
6. See if the email address is duplicate/already existing in the database.
Phone Number:
1. Check for valid/invalid phone number.
2. Test the field with leading/trailing spaces and for its maximum length.
3. See if the phone number is duplicate/already existing in the database.
4. Test if the email address shows an error message when left blank.
5. Check if the last name field allows numbers only.
6. See if the phone number field shows an error message for alphabets and special characters entry.
Username:
1. Check for existing and valid usernames.
2. Check for invalid usernames with wrong characters, such as #, $, and -.
3. Test the field for case sensitivity and maximum length of the input characters.
4. See if the field allows alphanumeric input as per user specifications.
5. Check if an error message is shown for using an existing username.
6. Verify if the system trims the whitespace and accepts the username.
Password:
1. The password should be a minimum and maximum characters long.
2. The password should have at least 1 uppercase and 1 lowercase letter.
3. Password should consist of at least 1 number.
4. The field must have at least 1 special character.
5. The password should not be the same as the username.
6. Test if the input in the password matches with the confirm password fields.
7. Check that error messages are shown for blank password field.
To Test a Newly Developed Music App in the Mobile ,below are some of the points to be considered to improve a listening experience for the users.
Registration:
Getting to the most used streaming music app is as basic as you can even think with all the base data and personalization, as the registration process on the app is free.
2. User Profile and Approval:
Installed with endpoints to recover an entire data about a person’s profile and approval of each user with the same database of user, for example, email address, Password and so on helps in limiting the spam intervenes.
3. Login and Sharing with Social Media:
Registration can even be easily accessed through online networking systems for additional memberships.
Additionally, with the development of social media networks, users are able to share anything they loved with their friends and family members.
So, maximum music streaming platforms also offer various sharing options, incorporating a probability to follow friends and share content.
4. Music Streaming:
An intriguing component that enables the music app user to remain notified on the latest launch of blockbuster tracks.
A person can tune in to the most recent collection on various music tracks whenever he or she wants to.
5. Suggestions and recommendations as per user’s music choice
A Personalized system to control all the tracks based on the user particular taste in music for a creating a compelling safe platform.
A user can find up as many numbers of tracks and spot the top choices.
The music streaming app can use an algorithm to slowly figure out the music choices of every app user which is one of the most engaging concepts in the advanced music applications industry nowadays.
Exploit deep learning techniques and make this factor a component of your future music streaming application.
Also, music streaming app users ought to have the capacity to locate their favorite artists, songs, music genres, trending music etc. as well as find new releases or genres.
With an advanced search option, they’ll have the capacity to discover precisely what befits their music tastes with an ease and in a very less time.
6. Playlists and presets creation
It is always a good choice to give users a chance to make their very own playlists for various activities and moods.
This feature doesn’t restrict here, as one can even be allowed to share their playlists with different users of the music application.
7. Able to save music when offline
This factor proves to be very useful in the circumstances when individuals are traveling anywhere and are having a hard time to get Wi-Fi or Mobile Internet access.
Functional Testing
Functional testing of music app generally includes a user interface.
A tester will check the application is performing the proposed functions, as directed by the business strategies or described in the specifications.
Functionality testing is performed to eradicate problems like:
Issues in connection speed
Vague error message
Application loading and speed issues
Bugs and crashing
Errors when screen sizes vary
Non-functional Testing :
Mobile App Performance Testing: Assesses the overall system performance, a process that involves measuring system response time, and measuring the response time of the crucial app elements. It can also be carried out as part of system testing as well as integration testing.
Stress testing: Validating the system performance in the context of scarce resources, which involves running tests on low storage/memory configurations to identify bugs that may be undetectable in normal circumstances. It also validates the app consistency when a number of users are executing the same action with the same data set and many client machines are connected to a number of servers, all subjected to varying degrees of system stress.
Load testing: Measures performance in scenarios of normal usage, repeated with a number of users to assess the consistency of the app response times. This should ideally be carried out at specified, customized, dedicated servers that closely simulate the real-world environment and expected usage scenarios.
Volume testing: Judges performance in the context of enormous amounts of data, involving an identification of where exactly the app fails and at what volume of data the system cannot continue running. A database is also created at the largest size possible, and many client queries are fed into the system to test how the app handles this kind of volume.
Usability testing: Basically, to assess user-friendliness, GUI consistency, error reportage, and correct output in line with the business-specified requirements.
UI testing: Issues addressed here include layout, data movement from one page to another, and pop-ups for assistance if the system concludes that a user needs guidance.
Recovery testing: Validates if the app shuts down during failure without glitches and without affecting the system, and the data is not lost. Such testing involves premature interruption or termination of data processes, manual dismantling of database keys and fields, as well as even turning off routers, servers and disconnecting the wires to assess the effectiveness of the app recovery when all the systems are rebooted.
Compatibility testing: Checks overall compatibility with a range of operating systems, browsers, and devices at varying strengths of configuration. Also has to ensure that the test cases executed in functional testing are the same ones used here.
Instability testing: Checks the smoothness of installs and uninstalls and confirms that the app behavior remains steady if the disk space is limited. Also confirms whether all the app components are correctly installed and that updates occur at the designated intervals.