Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .env
Original file line number Diff line number Diff line change
@@ -1 +1 @@
SPRINT=sprint5
SPRINT=sprint5-with-bugs
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pls, revert this

57 changes: 57 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,62 @@
[![Run Playwright Tests 🎭](https://github.com/testsmith-io/practice-software-testing/actions/workflows/run-tests.yml/badge.svg)](https://github.com/testsmith-io/practice-software-testing/actions/workflows/run-tests.yml)



# 🛠 Repository Rules

To maintain code quality and a smooth development workflow, please adhere to the following rules:

### 🌿 1. Feature Branches
All feature development must take place in a separate branch.
* **Base branch:** Always branch off from `main`.
* **Naming convention:** `US-{your-storyID}`.

**Example:**
```bash
# Update main to the latest version
git checkout main
git pull origin main

# Create and switch to a new feature branch
git checkout -b US-E1.1
```

### 🧪 2. Local Development & Testing
Before requesting a Pull Request:
1. **Work on your code:** Make small, logical commits.
2. **Tester Verification:** Once you've completed your task, a tester must manually verify the changes in your local environment or a staging environment if available.

**Example:**
```bash
# Add your changes
git add .
git commit -m "feat: refactor login page UI"

# Keep your branch up to date with main
git fetch origin main
git merge origin/main
```

### 🔄 3. Pull Requests (PR)
When the feature is ready and verified:
1. **Push your branch** to the remote repository.
2. **Open a Pull Request** targeting the `main` branch.
3. **Automated Tests:** GitHub Actions will automatically run the Playwright tests on your PR.
4. **Review:** Wait for at least one approval before merging.

**Example:**
```bash
# Push your branch
git push origin feature/login-page-refactor

# Go to GitHub and open a Pull Request
```

### 🎭 4. Automated Testing
Every Pull Request automatically triggers the Playwright test suite.
* Check the **Actions** tab on GitHub or the PR status to see if tests passed.
* If tests fail, fix the issues and push new commits to the same branch.

# Default accounts

| First name | Last name | Role | E-mail | Password |
Expand Down
2 changes: 1 addition & 1 deletion init-data.sh
Original file line number Diff line number Diff line change
@@ -1 +1 @@
docker-compose exec laravel-api php artisan migrate:fresh --seed --force
docker compose exec laravel-api php artisan migrate:fresh --seed --force
4 changes: 2 additions & 2 deletions sprint5/API/.env
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,10 @@ LOG_DEPRECATIONS_CHANNEL=null
LOG_LEVEL=debug

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_HOST=practice-software-testing-mariadb-1
DB_PORT=3306
DB_DATABASE=toolshop
DB_USERNAME=user
DB_USERNAME=root
DB_PASSWORD=root

BROADCAST_DRIVER=log
Expand Down