So You Think You Know Git 🤔

Scott Chacon's FOSDEM 2024 talk on Git Tips and Tricks.

👀 Watch it on YouTube 👀

📚 Top 5 Usability Testing Books 📚

Usability testing is a crucial aspect of user experience design, focusing on evaluating a product or service by testing it with representative users.

Below are 5 highly recommended books on usability testing, each offering unique insights into the process, methodologies, and best practices:

1️⃣ “Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests” by Jeffrey Rubin and Dana Chisnell

2️⃣“Usability Testing Essentials: Ready, Set…Test!” by Carol M. Barnum

3️⃣ “Rocket Surgery Made Easy: The Do-It-Yourself Guide to Finding and Fixing Usability Problems” by Steve Krug

4️⃣ “Moderating Usability Tests: Principles and Practices for Interacting” by Joseph S. Dumas and Beth A. Loring

5️⃣ “Remote Usability Testing: Actionable Insights in User Behavior Across Geographies and Time Zones” by Judy Blostein and Nupoor Ranade

Description of these books at the 🔗 Link 🔗

❓ How Git Works - From Working Directory to Remote Repository

1️⃣ Working Directory:
Your project starts here. The working directory is where you actively make changes to your files.
2️⃣ Staging Area (Index):
After modifying files, use git add to stage changes. This prepares them for the next commit, acting as a checkpoint.
3️⃣ Local Repository:
Upon staging, execute git commit to record changes in the local repository. Commits create snapshots of your project at specific points.
4️⃣ Stash (Optional):
If needed, use git stash to temporarily save changes without committing. Useful when switching branches or performing other tasks.
5️⃣ Remote Repository:
The remote repository, hosted on platforms like GitHub, is a version of your project accessible to others. Use git push to send local commits and git pull to fetch remote changes.
6️⃣ Remote Branch Tracking:
Local branches can be set to track corresponding branches on the remote. This eases synchronization with git pull or git push.

From Head of QA to Freelancing

In today's video, I had the pleasure to interview Leonardo Lanni. Leonardo has more than 15 years of hands-on experience in software testing. He worked for different companies from software tester to Head of QA. At some point in his career, he switched to freelancing. For me, this sounds like leaving the comfort zone, and is a great example for growth! Have a look at the interview to hear the full story of Leonardo!

https://youtu.be/l2U-4fd--n4?si=rDMSWzBiMYnC0NX5

Examples of SOLID Principles in Test Automation👨🎓

As the demand for high-quality software continues to increase, the role of SDET (Software Development Engineer in Test) has become increasingly crucial. SDETs are tasked with ensuring that the software being developed meets the necessary quality standards, and test automation plays a vital role in achieving this objective. However, as test automation code expands in size and complexity, it becomes susceptible to issues like code duplication, tight coupling, and fragile test suites. This is where the SOLID principles come into play.

S — Single Responsibility Principle
O — Open/Closed Principle
L — Liskov Substitution Principle
I — Interface Segregation Principle
D — Dependency Inversion Principle

🔗@jignect/examples-of-solid-principles-in-test-automation-0f41ff71e84e" target="_blank">Read full article 🔗

Hello, friends!👋
Nice cheat sheet “Top 9 HTTP Request Methods”.
If you have something to share, feel free to do so😃

LLMs to write selenium for automated web actions🤯

LaVague is an open-source project designed to automate menial tasks on behalf of its users. Many of these tasks are repetitive, time-consuming, and require little to no cognitive effort. By automating these tasks, LaVague aims to free up time for more meaningful endeavors, allowing users to focus on what truly matters to them.

By providing an engine turning natural language queries into Selenium code, LaVague is designed to make it easy for users or other AIs to automate easily express web workflows and execute them on a browser.

One of the key usages we see is to automate tasks that are personal to users and require them to be logged in, for instance automating the process of paying bills, filling out forms or pulling data from specific websites.

⬇️📚 Docs 📚⬇️
- https://docs.lavague.ai/en/latest/docs/integrations/hugging-face-api/
- https://github.com/lavague-ai/LaVague

UNTANGLE Spring Security Architecture 🔒

Authentication and Authorization:
- Validates user identity and orchestrates controlled resource access.
- Empowers comprehensive user authentication and nuanced authorization.

Security Filters:
- Intercepts incoming requests, meticulously enforcing security measures.
- Offers a flexible, layered security filter chain for diverse protection strategies.

Custom Authentication Providers:
- N Authentication Provider: Extends authentication capabilities beyond default configurations. Facilitates tailored authentication strategies and seamless integration.
- DaoAuthentication Provider: Adopts a database-backed approach for user authentication. Scrutinizes user credentials against stored records, heightening security.

Authentication Manager:
- Orchestrates the authentication process, coordinating various authentication providers.
- Serves as a pivotal component in managing user identity verification.

Token-based Security (JWT):
- Implements advanced token-based authentication for stateless communication.
- Facilitates secure interaction without the need for server-side storage.

Session Management:
- Efficiently manages user sessions, mitigating session-related risks.
- Provides adaptability for session creation, tracking, and invalidation.

Authentication Tokens:
- Username Password Authentication Token:Represents user credentials for authentication purposes.
- Leverages usernames and passwords for robust user verification.

Add/Remove Authentication Token:
- Dynamically enables the addition and removal of authentication tokens.
- Ensures real-time control over user authentication, promoting flexibility.

𝗚𝗶𝘁 𝗠𝗲𝗿𝗴𝗲 𝘃𝘀 𝗥𝗲𝗯𝗮𝘀𝗲

One of the most powerful Git features is branching. Yet, while working with it, we must integrate changes from one branch into another. The way how to do this can be different.

We have two ways to do it:

𝟭. 𝗠𝗲𝗿𝗴𝗲

When you merge Branch A into Branch B (with 𝚐𝚒𝚝 𝚖𝚎𝚛𝚐𝚎), Git creates a new merge commit. This commit has two parents, one from each branch, symbolizing the confluence of histories. It's a non-destructive operation, preserving the exact history of your project, warts, and all. Merges are particularly useful in collaborative environments where maintaining the integrity and chronological order of changes is essential. Yet, merge commits can clutter the history, making it harder to follow specific lines of development.

𝟮. 𝗥𝗲𝗯𝗮𝘀𝗲

When you rebase Branch A onto Branch B (with 𝚐𝚒𝚝 𝚛𝚎𝚋𝚊𝚜𝚎), you're essentially saying, "Let's pretend these changes from Branch A were made on top of the latest changes in Branch B." Rebase rewrites the project history by creating new commits for each commit in the original branch. This results in a much cleaner, straight-line history. Yet, it could be problematic if multiple people work on the same branch, as rebasing rewrites history, which can be challenging if others have pulled or pushed the original branch.

So, when to use them:

🔹 𝗨𝘀𝗲 𝗺𝗲𝗿𝗴𝗶𝗻𝗴 𝘁𝗼 𝗽𝗿𝗲𝘀𝗲𝗿𝘃𝗲 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗵𝗶𝘀𝘁𝗼𝗿𝘆, especially on shared branches or for collaborative work. It's ideal for feature branches to merge into a main or develop branch.

🔹 𝗨𝘀𝗲 𝗿𝗲𝗯𝗮𝘀𝗶𝗻𝗴 𝗳𝗼𝗿 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗯𝗿𝗮𝗻𝗰𝗵𝗲𝘀 or when you want a clean, linear history for easier tracking of changes. Remember to rebase locally and avoid pushing rebased branches to shared repositories. Also, be aware 𝗻𝗼𝘁 𝘁𝗼 𝗿𝗲𝗯𝗮𝘀𝗲 𝗽𝘂𝗯𝗹𝗶𝗰 𝗵𝗶𝘀𝘁𝗼𝗿𝘆. If your branch is shared with others, rebasing can rewrite history in a way that is disruptive and confusing to your collaborators.

Hello, friends!👋

Our QA community also appeared on LinkedIn:

– Real cases: how to market yourself to an IT company?
– QA news, research, and statistics ℹ
– Unique content! 🆕
– Workshops🤓
– Meetups 📢
– Case studies and expert opinions 👨‍🏫
– Manuals, checklists, and guides ⚙
– Info about internship programs 💼
– Sparkling professional humor 😎
– Answers to FAQs ❓
– Tips and life hacks 👨‍💻

Follow us on 🔗LinkedIn 🔗

20 Usability Testing Tools & User Testing Software 2024

Choosing the right usability testing tool can be overwhelming. To save you time, money, and sanity we created our list of the 20 best remote usability testing tools. Find the perfect match for you!

6 factors we evaluated for each usability testing software:
Features
Best for use cases
Recruitment options
Cost
Offered support
User reviews

20 remote usability testing tools & user testing platforms:
1. UXtweak
2. UserZoom
3. Lookback
4. Hotjar
5. UserTesting
6. UsabilityHub
7. Optimal Workshop
8. Userlytics
9. Useberry
10. Userfeel
11. Userbrain
12. Loop 11
13. PlaybookUX
14. UXarmy
15. Maze
16. TryMyUI
17. Proven by Users
18. Crazy Egg
19. Userpeek
20. Ballpark

🔗 See more information about this tools