Features
Features:

Product Tour >

Edraw AI >

Paid Plans:

Individuals >

Business >

Eduaction >
Resources
Blog

History

How-tos & Tips

Discovery

Biography

Business Analysis

Examples

AI concept Map

Free AI Mind Map Generator

Onenote Mind Map

Bcg Matrix Examples

Nike Marketing Strategy

Unilever SWOT Analysis

Make Mind Maps in Google Docs

Guide

FAQs

What's New

Resource Center
Templates
All Templates

Brain Storming Templates

Strategy and Planning Templates

Project Management Templates

Product Management Templates

Human Resources Templates

Agile Workflow Templates

Marketing Templates

Education Templates

Fun and Games Templates

User Gallery
Download
Pricing
Enterprise

MindMap Gallery Chapter 5 tpshop project actual combat (stage three)

Chapter 5 tpshop project actual combat (stage three)

Basic learning of software testing - Chapter 5 tpshop project actual combat (Phase 3), divided into 1. tpshop environment construction, quick familiarity with the project, test process, familiarity with the database, carousel chart, and shopping cart, suitable for beginners to understand and watch.

Edited at 2023-05-07 08:27:56

PlotWizard

Recent works View more works>>

Chapter 5 tpshop project actual combat (stage three)

PlotWizard

Recent works View more works>>

Recommended to you
Outline

Chapter 5 tpshop project actual combat

1. tpshop environment construction

1.1 Introduction to basic environment

1.2 tpshop environment setup instructions

1.3 tpshop sets local domain name extension

2. Quickly familiarize yourself with the project

2.1 Familiar with project steps

Business features

Users and roles

Organization Chart

technology stack

2.2 Be familiar with information sources

Find documents: , such as requirements specifications, user manuals, test cases, etc.

Existing environment: such as development environment, test environment

People: Such as developers, product managers, team leaders

2.3 Be familiar with the business characteristics, users and roles of the tpshop project

Business features: tpshop is an open source e-commerce system

Roles and users:

front desk

Visitors, , registered members

Backstage:

Super administrator, warehouse manager, customer service

2.4 Be familiar with the organization chart drawing background of the tpshop project

Reflect the organizational relationship between subsystems and elements, each module and the submodules under each module, and the organizational relationship between submodules under the submodules.

Function: Comprehensive understanding of the items being tested

Draw:

Backstage

System > Subsystems > Modules > Submodules

See specific page deadlines

front desk

tpshop purchase process

2.5 Be familiar with the background comments on the organization chart drawing of the tpshop project

2.6 Be familiar with the front-end rules for drawing the organization chart of the tpshop project

Front desk rules:

An independent page is a module

Modules with common features can be summarized and merged

2.7 Familiar with the organization chart drawing and front-end combing of the tpshop project

2.8 Be familiar with the tpshop project technology stack

Database: MySQL

web server: Apache

Development language: PHP

Operating system: window (Linux)

3.Testing process

Requirements analysis and review

How to do a needs review?

1. Requirements review meeting

2. Participants

Product Manager/Project Manager

Development/UI

test

DBA

.....

What are the main responsibilities of a test engineer in a requirements review?

Confirm that the person understands the needs and has no objections

Confirm that the requirements have no obvious errors or doubts

Confirm that the requirements have no obvious errors and can support subsequent use case design, etc.

Make some suggestions for improvements

Review case 1

Write test plans and test solutions

Test Plan

Concept; a document that describes the scope, methods, resources, and schedule of testing activities to be performed

Test program

Concept: Analyze the requirements from the technical perspective of testing, clarify the direction of how to test, focus on the analysis results and technical implementation

core content

method

environment

tool

Design test cases and review

Basic testing strategy

Smoke testing Single function testing Integration testing and regression System testing and regression Acceptance testing and regression

Core elements of test cases

ID module priority title test data preconditions test steps expected results

Key points of test cases and defect reports

Core elements of defect templates

ID Title Priority Severity Preset conditions Test data Reproduction steps Expected results Actual results Defect type Defect status

Write test report

4. Familiar with databases

5.Carousel chart

6. Shopping cart

Chapter 5 tpshop project actual combat

7.Member list

8. rush buying

9.Non-functional

1. Compatibility testing

Major browsers

2. Interface testing

Refer to UI design drawing

3. Usability test

Focus: user groups, computer level, project complexity, tab/enter, etc.

4.Performance testing

(Concurrency testing, stress testing, load testing)

5. Security

Test business concerns (business level)

Input (sensitive information occlusion test), transmission (data needs to be encrypted, there is complexity), output (sensitive information needs to be encrypted),

10. Use case review summary

Test Data

Pay attention to the timeliness of test data (test preparation)

For example, the mobile phone number used during registration was unregistered when it was registered for the first time, and becomes registered when it is registered for the second time. In certain data situations, we can omit these test data.

The title and expected results should be clear

Note: If there is no similar error message in the requirements, we should set the expected results of the use case with the help of other similar types or messages.

test title

Directly state the purpose of the test

Be concise and to the point, not too lengthy

For example, when testing exceptions, just focus on the abnormal conditions. (Other correct parameters can be put aside. Other normal parameters do not need to be written under the rules agreed in actual work.

If it is a normal class test, the test cases can be subdivided according to the effective equivalence categories.

Titles generally do not repeat

priority

When designing test cases, should they be based on the requirements specification or the system?

Companies with standardized processes must design test cases based on requirements specifications (or prototype diagrams)

Looking at the time point when entering the project node

Initial intervention, based on the requirements statement

Intervention in the middle and later stages, based on the requirements statement

It is possible that during the actual testing process, there is no requirement specification, and you can refer to the current system.

Project maintenance intervention stage, based on the requirements specification

It is possible that during the actual testing process, there is no requirement specification. You can refer to the current system, user manual, bug list, etc.

11.State migration

concept

Based on a product specification analysis, each state of the system and state-related functions are tested, and the logical flow of the verification program is passed through different states.

First, find out all the states of the object being tested, then analyze the transitions between the states, and establish a design method for test cases based on this.

Note: State migration does not guarantee the correctness of a single function point, but only guarantees whether the transition between states is consistent with the requirement description.

scenes to be used

When designing use cases for complex business scenarios

step

1. Clarify the status nodes: Analyze the requirements specification of the object being tested, and clarify the number of status nodes of the object being tested.

2. Draw a state transition diagram: Use circles to represent state nodes, and arrows to represent the migration relationships between states.

3. Draw the state migration tree: Draw the state migration tree according to the nodes and arrows of the state migration diagram (first clarify the starting node and ending node

4. Find the transition path between states

12.Flowchart

represent

Ellipse: start/end

Arrow: path, the direction of the process

Parallelogram: data input and output

Rectangle: process/step/process

Diamond: Judgment/Judgment

in principle

The process is correct and no path is missed

Determine first, then determine the result

The main process is kept in the middle of the flow chart for easy reading

13.Database

Application scenarios

Accuracy and completeness of Yanzeng data

Defect location using database

Rescue database to construct test scenarios (requires specific test data)

Update with database data backup

14. Capture packets

concept

It is to intercept, resend, edit, dump and other operations on the data packets sent and received during network transmission, and is also used to check network security.

tool

fiddler（PC）

Unsafe, can only be queried, cannot transmit sensitive information, is exposed on the URL, the request parameters will be retained, the request parameters have a length limit, and only ASCII characters are accepted

Supports multiple encodings, can carry sensitive information, request parameters will not be retained, there is no length limit (depending on the browser), and there is no character limit

charles(mobile phone)

f12 development tools

Set filtering

Modify request

Respond to modifications

automatic response

HTML and HTTP protocols

URL: Uniform Resource Locator

Format: Protocol --- IP or domain name ---- Port number (http: 80, HTTPS: 443, ssh: 22) ------ Resource path ---- Parameters: (use ? separated from the body of the URL ; Format: parameter name = parameter value. If there are multiple parameters, use the & symbol to splice them together.

http: Hypertext Transfer Protocol

HTML: Hypertext Markup Language