Test Plan 3Do Websites - Find Jobs.pdf

TEST PLAN

3Do WEBSITES - FIND JOBS

1 Bùi Chí Cường – CE172056 (Leader)2 Trương Quang Thắng – CE1716843 Nguyễn Bảo Lộc – CE1714854 Lê Tấn Kim – CE1704695 Đặng Phước Ân – CE171980

TABLE OF CONTENTS

I INTRODUCTION 4

II TEST OBJECTIVE 5

III SCOPE OF TESTING 5

a Features Not To Be Tested (Out of scope) 5

b Features To Be Tested (In scope) 5

IV TEST STRATEGY 7

VIII TEST ENVIRONMENT 11

IX SCHEDULE & ESTIMATION 12

VERSION HISTORYVersio

0. I INTRODUCTION

I In the ever-evolving world of work, online job search websites have transformedthe way people connect with employment opportunities Fueled by the rising need forefficient and accessible job hunting, these platforms have become essential tools for bothjob seekers and employers They function as virtual career marketplaces, offering a vastselection of job postings across various industries and fields.

II The core purpose of an online job search website is to empower users to explore,apply for, and secure jobs from the comfort of their devices By harnessing the potentialof the internet, these platforms provide a streamlined and user-friendly experience,allowing job seekers to browse a comprehensive database of positions, filter by skills andexperience, and directly connect with potential employers.

III This approach fosters a dynamic environment where qualified candidates canefficiently showcase their talents and employers can discover a pool of top prospects Byfacilitating a smooth and efficient job search process, online job search websites play acrucial role in connecting the right people with the right opportunities.

Team Members

- Responsible for all aspects of the job.- Determine its goals.

- Collect necessary data.

- Name and explain the proper test methods, instruments, and automation architecture.- Check and evaluate the test strategy.- Complete the tests.

- Note test findings and report any errors discovered.Nguyễn Bảo Lộc Developer in Test

- Implement the test cases, test program, test suite.

- Builds up and ensures test environment and assets are managed and maintained

- Support Tester to use the test environment for test execution

- Take in charge of quality assurance

- Check to confirm whether the testing process is meeting specified requirements

II TEST OBJECTIVE

Objectives of document checking:Determine scope and features:

- Break down the goals, scope, and core principles of site scraping.- List all the site's features, modules, and integrations.

- Clearly define which features will be tested and which will not.

Ensuring smooth operation:

- Check if the website works properly and without problems in a real environment.- Use real-world data and scenarios to test site functionality in simulated search scenarios.- Test the website's performance when many users access it at the same time.

- Ensure website functionality meets all business requirements.

User interface (UI) review:

- Check that the user interface and other external interfaces of the website functionaccording to the correct design and meet the user's needs.

- Ensure your website's user interface is guided by best practices, easy to use and accessible.- Test for maximum user interface functionality across all pages and platforms.

- Ensure the website's user interface is both validated and meets user expectations.

Evaluate user experience (UX):

- Evaluate the convenience and user-friendliness of the website.

- Test the ease of use of the search, creation, and navigation functions on the site.- Make sure the content on your website is easy to read and well organized.- Ensure the overall interface of the website is friendly and easy to use.- Ensure device performance and compatibility:

- Determine the devices and browsers the website must be compatible with.

- Testing tests the strategy to ensure your website works on all popular browsers andsupported devices.

- Estimate the cost and resources required to test your website across multiple browsers.

III SCOPE OF TESTING

a Features Not To Be Tested (Out of scope)

● Software Interfaces

● Hardware Interfaces

b Features To Be Tested (In scope)

User Interfaces

● Functional Item: This test plan document is applicable for testing thefunctionality of Online Shoes Providing Websites Services and functions tocheck:

1 Login/Logout All actors This feature allows all agents to log in to the systemby providing a valid username and password Oncelogged in, all actors can log out and have access totheir respective location functions.

2 Register Companies, candidates

The feature allows users to create a login accountby entering email, phone number, name, andaddress.

3 Staffs Management Admin, company Employee management helps administrators andcompanies manage, inventory, and secure data forusers.

4 Post jobs Staff Post management helps administrators monitorposts and ensure there are no errors in the posts.5 Search Jobs Candidate Allows candidates to search for information about

job postings.

6 View and Edit profile All actors Allows checking and updating personal informationsuch as name, email, address, and other personalinformation

7 Company management

Admin Admin can approve registration for recruitment, bychecking tax code.

8 Search Candidate Staff Allows staffs to search for information aboutcandidate news.

9 Candidate management

Admin Candidate management helps administrators andcompanies manage, inventory, and secure data forusers.

10 Apply job Candidate Candidates can apply to recruitment posts, if theyfeel they are suitable for the position of the post

● Non-functional item:

o Check that the website complies with all relevant TRUSTe and HIPAAregulations.

o To ensure user data is safe, check the website's security measures.

o Make sure your website's privacy policies and procedures are thorough and easyto understand by testing them.

o Calculate load times of various web pages in typical cases.o Check that every page loads in three seconds or less.

o If any pages take longer than three seconds to load, find out why and look into theissue.

o Check whether the registered tax number matches the state tax number

IV TEST STRATEGYa Test Types

1 User Interface Testing

Test Objective: Verify that the website's user interface (UI) provides an online job search

that is easy to use and navigate, and meets all user needs.

understandable and instructive.

- Testers will carry out the test cases and document their findings.- Testers will notify the development team of any flaws they discover.

Completion Criteria:

- Every UI test case has been run and found to be successful.- Every UI flaw has been fixed, with the exception of those that the customer approved.

- Every flaw that the testers discovered has been fixed in the defect management system (DMS).

● Delete staff● View profile

● Search for jobs and candidates● Apply jobs

- Testers will execute test cases and record the results.- Testers will report any errors found to the development team.

Completion Criteria:

- Every functional test case has been run and passed;

- Every website functionality issue has been resolved, with the exception of those that the customer approved.

- The defect management system (DMS) contains fixes for every flaw that the testers discovered.

Special Considerations:

Unit and integration testing should be finished before the development team begins functional testing.

3 Load Testing

Test Objective: Verify that the online shoes providing website can handle a large number of

concurrent users without performance degradation.

- Performance metrics such as page loading time will be measured by testers.

- Testers will examine the outcomes to find any areas where performance is impeded.

Completion Criteria:

- All of the website's pages must load in three seconds or less when there are100 or fewer concurrent users.

- In high-stress scenarios (more than 100 concurrent users), all website pages should load in six seconds or less.

- All performance standards need to be fulfilled.

Special Considerations:

- To replicate the various ways that users will access the website, testers should make use of a range of hardware and browser combinations.- In order to make sure that the website can scale up efficiently, testers should progressively increase the number of concurrent users.- Throughout the load test, testers should keep an eye on the website's functionality to spot any early warning indications of issues.

b Test Levels

Types of TestStages of Test

User Interface test X

c Supporting Tools

Documenting MS Word, Excel Microsoft 2016Automation testing Katalon KMS Technology 5.8.3Unit Testing JUnit The JUnit TeamDatabase SQL Server Microsoft 2019

V RISKS

Members of the team lack the

necessary abilities for testing websites Suggest looking for external information and watching tests on different platforms like facebook, youtube, to help team members better understand testing.

Time is of the essence; meeting deadlines is challenging

Set aside appropriate time for every test phase.

Having trouble accessing the test Learn more about the tool and how to use it.

VI TEST CRITERIA

Entry Criteria for Website TestingPrerequisites:

+ Hardware: Computers must have a stable internet connection.

+ Testers must have adequate knowledge of the website and job search processes.+ The testing plan must be finalized.

+ The test case suite must be ready.

+ The testing environment and resources must be fully prepared.

Testing can only commence once all of the above conditions are met.Examples: * System testing cannot begin if the test cases are not yet complete.

* Testers must have sufficient knowledge to understand the website andperform effective testing.

Suspension Criteria for Website Testing

+ Failure Rate: If more than 40% of test cases fail, testing should be suspended to notifythe development team for bug fixing before proceeding.

Example: * If severe bugs are detected during testing, testing should be suspended for the

dev team to fix them first.

Exit Criteria for Website Testing

+ Run Rate: All test cases must be executed successfully (100% run rate).

+ Failure Rate: The test case success rate must be above 95% (only minor bugs that do notaffect core functionality are acceptable).

Only when both of the above conditions are met is the website testing processconsidered complete.

VII RESOURCE PLANNINGa System Resource

3 Network Setup internet line with the speed at least 5 Mb/s

- Work together with other departments to make sure the testing procedure runs smoothly.- Notify the appropriate parties of the test results.

VIII TEST ENVIRONMENT

- Device: Laptop, Desktop, Mobile- Operating System: Windows 10/11- Browser:

+ Google Chrome+ Microsoft Edge+ Brave- Network: Wi-Fi

- Database: Microsoft SQL Server 2022

IX SCHEDULE & ESTIMATION

SCHEDULE TO COMPLETE TASKS

X.TEST DELIVERABLESBefore testing:

+ Test Plan: A detailed plan of the scope, goals, strategy and resources needed forthe testing process.

+ Test case set (Test Case Documentation): Document that lists each specific testscenario, including implementation steps, expected input data and expected outputresults.

+ Specific Requirements for Test Design: Any special requirements related to testcase design, such as standards for level of detail or prioritized test cases.

During testing:

+ Testing Tool: Software that supports the execution of test cases automatically orsemi-automatically, helping to save time and effort (Example: Selenium, Cypress)+ Test Data: Data used to run test cases, including valid and invalid data to testwebsite features in different situations.

+ Simulation: Create hypothetical situations to test whether the website operatesnormally under high load conditions or unusual exceptions.

+ Log Errors and Execute Log: Record all errors encountered during testing andtest case execution for easy tracking and analysis.