APP manual testing 01-app special test points - test development environment - Agile

APP special test points

  • Compatibility Test

  • Install, uninstall, upgrade

  • Crossing event

  • PUSH message push test

  • Performance Testing

  • Other types

 

Compatibility Test

  • Phone model

  • System Version Android (version 4.4 start compatible) IOS (version 9.x start compatible)

  • Screen size, resolution

  • Network status 4G, WIFI

Traffic statistics platform Baidu hospital https://mtj.baidu.com

  • Brands

  • model

  • Resolution

  • system

  • networking

Priority compatible model.

Compatibility testing and pay attention:

  • After functional testing, compatibility testing

  • Compatibility tests focus on the page display: overlaps, whether to display the complete layout, page alignment

  • Can put together the mobile phone emissions when tested, tested simultaneously.

Install, uninstall, upgrade

  • Install / uninstall on different devices

  • An exception occurred during the installation process, you can continue to install or uninstall and then install

  • An exception occurred during the uninstall process, you can continue to install or uninstall again

  • When the software upgrade, users can see the new version tips

  • Cross-version upgrade, can upgrade directly from the old version to the latest version

  • The upgraded software, data stored on the device can continue to use the software

  • It can choose whether to delete the data when uninstalling software

Cross-event test

Conflict test, interference test

  • APP is running to answer the call

  • Receive information APP runtime

  • Network switching on / off, 4G / WIFI

  • The phone comes with the application of interference, camera, calculator, calendar

  • APP is running, and plug the charger / headset plug

  • APP is running, back to the desktop, lock screen, voice assistant

 

PUSH Messaging Test

  • Push-according to business rules

  • Object Push push follow, specific individual user, some users groups, all users

  • When the user sets does not accept the notification message, push message should no longer appear

  • When users log off the account, when the account log in again, you should be able to receive push content before

  • When mobile phone users off the network connection again, should be able to receive push content before

  • After re-reading the message, a message should be canceled

  • Phone running in the background after the foreground, showing the message should be different

Performance Testing

APP is mainly reflected in the performance of CPU, memory, power, flow, start speed, interface switch

  • APP's start time,

    • Hot start: Wake software from running in the background

    • Cold start: the software is completely closed from the start

  • CPU and memory footprint attention APP

    • Out of memory: memory is larger than the remaining application memory

    • Memory Leak: Memory is not released after use

  • APP flow of power consumption and consumption

  • When APP prolonged use, the phone's software processes and system resources

APP optimize performance:

  • Image compression cut

  • Picture cache

  • Information "pull down to refresh", equivalent to the information page display

Other types of tests

The user experience, extreme circumstances (border), device permissions

  • Interface tidy and beautiful

  • APP when running memory / storage memory will be used up, software installation / use

  • APP in low battery use, the sudden power shutdown

  • APP in the absence of rights camera configuration, the function uses the camera case

  • More permissions: album, telephone, positioning, Internet, recordings

  • Use of special equipment, the slide to the left screen, the switching 3D-touch, the screen of the horizontal and vertical screen

 


 

APP project environment

  • Development environment

  • test environment

    • Code control environment remains stable and can not modify

    • Control the user environment, the test data to avoid arbitrary changes

  • Production / line environment

In stages:

Development (development environment: integration and code for developers to self-test) ---- test (test environment) ----- on-line (production)

Testers whether or not to be tested in a production environment? We need to test

  • Software upgrade process can go wrong (code, database, configuration files)

  • There are different production and test environments

    • Different hardware environment

    • Different network environments

    • Data different sites, different amounts of data level

    • Server configuration file different

Testing Tips:

Special account reserved for the production environment and test data,

If allowed, the internal testing process, cutting production processes connected to the Internet. After the test is completed, it restores the data state production environment.

Was added a test environment between the test and production environments, to simulate the production environment (as close as possible)

Pre-release environment, production-like environment

  • Use a recent production data state as a database for testing

  • Hardware environment, network environment, the configuration file as close to the production environment of state

Step: Associate production test environment --- ----- production (selection of important functions, a greater risk of functional testing to ensure that the upgrade process correctly)

 

APP closed beta

Installation package: Android apk IOS ipa

Internal distribution platform

  • Dandelion: The account login, upload the application, after the release to generate two-dimensional code, scan code to download and install

  • fir.im

 

APP released online

Andrews: The Po, 360 mobile assistant, pea pods, major mobile phone brand application store

IOS:APP Store

 

Agile development concept

The concept: the user needs as the core, using an iterative, incremental approach to software development

Internet Features:

  • Slow to fast food

  • Highly uncertain demand

  • New needs, new direction

  • We need to try to avoid project risk, rapid trial and error, to get fast feedback

 

Four values ​​agile development model

Individual and interactive than processes and tools

Working software is higher than exhaustive documentation

Customer cooperation than contract negotiation

Respond to changes than following a plan

 

Scrum in three roles

  • Product Owner Product Owner

    • Identify needs, forming a to-do list backlog, and prioritize

    • Determine the product's release date

  • Project Manager Scrum Master

    • The smooth progress of administrative tasks to keep team productivity

    • Protection team is not something else interference

    • Ensure that relevant team members have the ability to complete tasks

  • The development team (5-9) Dev Team: implementation requirements, completion

    • test

    • Develop

    • interface

 

Scrum development process

  • Product manager collected demand, determine the product feature list

  • Planning meeting: to discuss with the task iteratively determine product manager, project manager, the development team

  • Daily legislature: the development team communication problems encountered, the date of the work plan, task breakdown

  • Will be assessed: product managers, project managers, development team, market-related personnel on the work product for final confirmation.

    • Review by the market

    • Assessment is not passed, continue to be modified to adjust

  • Will reflect: the project manager, the development team good practice for the next iteration cycle, the need to improve the work summary of the discussions, in order to help complete the next iteration of the task.

Agility signboard

  • Work transparency

  • Clearly indicate the state of progress of the demand / job

Daily meetings, around billboards introduced their work content.

APP testing process

  • Requirements Review: Planning Meeting

  • Test Plan: Determine iterative tasks

  • Test case: an iterative cycle of daily work

  • Test execution and tracking BUG: iterative cycle of daily work

  • Test report: Before the review meeting, you can do will reflect on the discussion of the contents of the report

Guess you like

Origin www.cnblogs.com/snailon/p/10927666.html