Tuncay Kaplan trkaplan

Playwright E2E Testing Guidelines

Test Structure and Organization

Store all tests under the tests/ folder
Name test files based on the system component being tested (conceptual, not React component)
Group related tests within a single file using test.describe blocks
Use descriptive test names that explain the functionality being tested
use test.use({storageState: ...}) for setting auth state across all test in the suite

Locator Strategy

[Project Name]

Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.

Project Context

[Brief description ]

[more description]
[more description]
[more description]

Çoğu proje Eslint konfigürasyonu ile geldiğinden ve editörümüzde eslint eklentisi kurulu olduğundan biliyor sanıyor olduğunuz bir şeyi netleştirelim: Sorun; build anında aldığımız eslint hatalarını kodu yazıp kaydettiğimiz anda otomatik düzeltilmesini sağlamak: (Eğer linterin bunu düzeltme imkanı varsa, çünkü bazı eslint uyarıları otomatik fixlenemiyor) Lint hatasını almışsak, projede bir linting konfigürasyonu var demektir. Editörde bu hataları görebilmek için eslint eklentisine ihtiyaç duyuyoruz. https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint

Editörde değişiklikler kaydedildiğinde linterın otomatik çalışması için de vs code için; settings.json içinde şu ayara ihtiyaç var:

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

	You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.

	Project Context: This is a dev tool built for evaluating open source projects allowing people to better understand the maintainability, activity and longevity of a given project to allow devs to better decide whether they should include or use the given open source repositories after the analysis

	Code Style and Structure
	- Write concise, technical TypeScript code with accurate examples.
	- Use functional and declarative programming patterns; avoid classes.
	- Prefer iteration and modularization over code duplication.
	- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
	- Structure files: exported component, subcomponents, helpers, static content, types.

	const fs = require('fs');
	const cp = require('child_process');
	const util = require('util');
	const path = require('path');

	const exec = util.promisify(cp.exec);
	const writeFile = util.promisify(fs.writeFile);

	const prettierConfigVscode = {
	'editor.codeActionsOnSave': {

	#! /bin/zsh --no-rcs --err-exit
	export PATH=node_modules/.bin:$PATH

	alias -g i=install

	if (($+commands[pnpm])) then
	local p=p
	alias pnpm=npm npx=pnpx
	# FIXME https://github.com/pnpm/pnpm/issues/1360
	npm config get -g global-dir \| read

	[
	{
	"name": "Huawei Y9s / P Smart Pro",
	"series": "Y Series",
	"userAgentFingerprint": "STK-L21",
	"screenSize": 6.59,
	"wRes": 1080,
	"hRes": 2340
	},
	{

	<!DOCTYPE html>
	<html lang="en">

	<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>iframe</title>
	</head>

	{
	"editor.quickSuggestions": true,
	"tailwindCSS.experimental.classRegex": ["tw`([^`])", "tw=\"([^\"])", "tw={\"([^\"}])", "tw\\.\\w+`([^`])", "tw\\(.?\\)`([^`])"],
	"tailwindCSS.includeLanguages": {
	"typescript": "javascript",
	"typescriptreact": "javascript"
	}
	}