Conduit Test Plan

Introduction

The “Conduit” application is designed as an open-source application to train software development and testing skills. The main website functionality includes registration and sign-in, posting articles on different topics, reading articles, the ability to like an article, posting a comment, and following users.

1.Test strategy

1.1 Testing scope

1.1.1 Features to be tested

Module name	Login type	Description
Home Page	Logged in	Users can see articles in Global Feed. Clicking an article preview opens the correct article. 'Your Feed' displays posts from followed users. The [Like] button works properly.
	Logged out	Users can browse articles but cannot interact (like, comment, or follow). The 'Popular Tags' section displays relevant tags.
Sign Up Page	Logged Out	Users can register with a username, email, and password. Validation errors appear for missing or invalid inputs. Successful registration redirects to the home page.
Sign In Page	Logged Out	Users can log in with valid credentials. Error messages appear for incorrect credentials.
New Article Page	Logged in	Users can create an article by filling out the title, description, content, and tags. Form validation works for missing fields. Published articles appear in the feed.
Settings Page	Logged In	Users can update profile settings (username, email, bio, password, and profile picture). The 'Update Settings' button works properly. Logging out redirects to the home page.
User Page	Logged In	User can view, edit, or delete their articles. The 'Favorite' button adds articles to the favorited list. The 'Edit Profile Settings' function works correctly.
	Logged Out	Users can view another user's profile and articles.
Article Page	Logged In	User can like, comment, edit, and delete their articles. Comments appear correctly. Tags are displayed properly.
	Logged Out	Users can read articles but cannot interact (like, comment, or edit). Tags and comments are visible but not editable.

1.1.2 Out of test scope

These areas are out of scope for this testing cycle:

Website Security
Website Performance
Website API testing
Test Automation

1.2 Test types

In this testing cycle, the Conduit website will be tested using the next testing types:

System testing: all the testing will be conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.
Exploratory testing.
Smoke testing for each new build.
Functional testing of all the features
GUI testing
Compatibility testing: test only Windows and MacOS browsers

1.3 Risks and Issues

Risk	Mitigation
Team members lack the required skills for website testing	Provide training sessions, and mentorship programs, and allocate experienced testers
Not enough time to test all browsers and OS.	Prioritize testing on the most used browsers and OS versions based on market share.
Not enough time to execute all test scenarios.	Focus on high-priority test cases first. Ensure critical features are validated.
A member of the team has got sick	provide cross-training team members to cover multiple roles

1.4 Test Logistics

1.4.1 Who will test?

QA engineer
QC engineer
Manual Testers
Automation Testers
Mentors

1.4.2 When will the testing occur?

The team will start the testing after:

Software is available for testing
Test specifications are created
The test environment is set up
Enough human resources are available

2. Test objective

The test objectives are to verify the functionality and API of the Conduit app. The testing should be focused on the flow of publishing articles and sharing information between members. The main features are authorization, posting new articles, following members, saving favorite articles on their pages, adding likes, and writing comments. Testing should be done on preselected versions of browsers and mobile devices described in the "System resource" section.

3. Test criteria

3.1 Suspension criteria

10% of P0/P1 tests failed, which should lead to the testing suspension until the development team fixes all the corresponding bugs.
30% of P2/P3 tests failed, which should lead to the testing suspension until the development team fixes all the corresponding bugs.

3. 2 Exit criteria

The test execution will be stopped no later than the last day of the sprint. The exit criteria should be met to complete the testing cycle:

The mandatory Execution rate is 95%.
The mandatory Pass rate is 100% for P0/P1 tests.
The mandatory Pass rate is 80% for P2/P3 tests.
All necessary artifacts collected: test cases, and bug reports.
The product should not have known bugs with severity Critical and Major and bugs with Priority High at the time of finishing testing.
The list of allowed bugs is agreed upon with the developers and managers.

4. Resource planning

4.1 System resources

No.	Resources	Description
1	Browser	Chrome, Firefox, Safari
2	Network	Stable internet connection min 20mb/s
3	Computer	Windows/Mac

4.2 Human resources

No.	Resources	Description of tasks
1	QA Engineer	• Defines test strategy, plans test execution, reviews defects, and ensures overall quality processes are followed.
2	QC Engineer	• Focuses on validating that the product meets business requirements, executes test plans, and ensures compliance with quality standards.
3	Manual Testers	• Execute functional, exploratory, and regression tests manually, documenting defects and reporting issues.
4	Automation Testers	• Develop and maintain automated test scripts, ensuring continuous integration and testing of key functionalities.
5	Mentors	• Guide and support the QA team, review test cases, suggest improvements and ensure the overall efficiency of testing processes.

Test environment

Testing should be conducted in the production environment. To run the app locally for working with DB we will use Docker.

6. Schedule & estimation

6.1 All project tasks and estimation

Task	Members	Estimate effort
Create Test plan	QA Engineer	5 man-hour
Create decomposition, decision table, state transition diagram	QC Engineer	10 man-hour
Create Test cases	Manual Testers	10 man-hour
Review Test cases	Mentors	3 man-hour
Test cases execution	Manual Testers Automation Testers	10 man-hour
Create Bug reports	Manual Testers	10 man-hour
Writing test report	QA Engineer	5 man-hour

6.2 Schedule to complete these tasks

Task	1-st Sprint	2-nd Sprint	3-rd Sprint
Create Test plan	✅
Create decomposition, decision table, and state transition diagram	✅
Create Test cases		✅
Review Test cases		✅
Test cases execution		✅ (partial), ➕ more in Sprint 3	✅
Create Bug reports		✅	✅ (continued)
Writing and preparing test results			✅

7. Test deliverables

7.1 Before the testing phase

Test Plan Document
Test Cases
Test Design Specifications

7.2 During the testing

Test Execution Reports
Bug Reports

7.3 After the testing cycle is over

Test Results
Final Test Report
Bugs Summary

BACK