{"id":925591,"date":"2024-08-12T01:37:44","date_gmt":"2024-08-12T01:37:44","guid":{"rendered":"https:\/\/proxyelite.info\/?p=925591"},"modified":"2024-08-12T01:37:45","modified_gmt":"2024-08-12T01:37:45","slug":"what-is-tdd-a-complete-guide-to-test-driven-development","status":"publish","type":"post","link":"https:\/\/proxyelite.info\/tr\/what-is-tdd-a-complete-guide-to-test-driven-development\/","title":{"rendered":"TDD Nedir? Test Odakl\u0131 Geli\u015ftirmeye Tam Bir K\u0131lavuz"},"content":{"rendered":"
Bak\u0131\u015f a\u00e7\u0131s\u0131<\/strong><\/th>Tan\u0131m<\/strong><\/th><\/tr><\/thead>
Tan\u0131m<\/strong><\/td>\u0130\u015flevselli\u011fi garanti alt\u0131na almak i\u00e7in koddan \u00f6nce testlerin yaz\u0131ld\u0131\u011f\u0131 bir yaz\u0131l\u0131m geli\u015ftirme yakla\u015f\u0131m\u0131.<\/td><\/tr>
Birincil Hedef<\/strong><\/td>Her kod par\u00e7as\u0131n\u0131n ama\u00e7lanan amac\u0131na uygun olmas\u0131n\u0131 sa\u011flayarak kod kalitesini art\u0131rmak ve hatalar\u0131 azaltmak.<\/td><\/tr>
\u00c7ekirdek \u0130\u015flem<\/strong><\/td>Bir test yaz\u0131n, \u00e7al\u0131\u015ft\u0131r\u0131n, kodu yaz\u0131n, t\u00fcm testleri \u00e7al\u0131\u015ft\u0131r\u0131n, yeniden d\u00fczenleyin ve tekrarlay\u0131n.<\/td><\/tr>
Temel Faydalar<\/strong><\/td>Erken hata tespiti, daha iyi kod yap\u0131s\u0131, daha kolay bak\u0131m ve kod de\u011fi\u015fikliklerine daha fazla g\u00fcven.<\/td><\/tr>
Pop\u00fcler Ara\u00e7lar<\/strong><\/td>JUnit, NUnit, PyTest, RSpec, Mocha ve TestNG.<\/td><\/tr>
Zorluklar<\/strong><\/td>Zihniyet de\u011fi\u015fikli\u011fi gerektirir, ba\u015flang\u0131\u00e7ta zaman al\u0131c\u0131 olabilir ve testlerin s\u00fcrd\u00fcr\u00fclmesinde disiplin gerektirir.<\/td><\/tr>
En \u0130yi Uygulamalar<\/strong><\/td>K\u00fc\u00e7\u00fck ve basit testlerle ba\u015flay\u0131n; testleri h\u0131zl\u0131 tutun; d\u00fczenli olarak yeniden d\u00fczenleyin; ve iyi bir test kapsam\u0131n\u0131 koruyun.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\n

Test Odakl\u0131 Geli\u015ftirmeyi (TDD) Anlamak<\/h3>\n\n\n\n

Test Odakl\u0131 Geli\u015ftirme (TDD), yaz\u0131l\u0131m geli\u015ftirme bi\u00e7imini d\u00f6n\u00fc\u015ft\u00fcren bir metodolojidir. Peki TDD tam olarak nedir ve geli\u015ftiriciler ve ekipler i\u00e7in neden \u00f6nemlidir? Bu makale TDD'yi derinlemesine inceleyecek, s\u00fcrecini, faydalar\u0131n\u0131, ara\u00e7lar\u0131n\u0131, zorluklar\u0131n\u0131 ve en iyi uygulamalar\u0131n\u0131 ke\u015ffedecektir.<\/p>\n\n\n\n

TDD'nin Temel S\u00fcreci<\/h3>\n\n\n\n

TDD, genellikle "K\u0131rm\u0131z\u0131, Ye\u015fil, Yeniden D\u00fczenleme" olarak \u00f6zetlenen sistematik bir yakla\u015f\u0131m\u0131 takip eder. \u0130\u015fte nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131:<\/p>\n\n\n\n

1. Bir Test Yaz\u0131n<\/h4>\n\n\n\n

Herhangi bir kod yaz\u0131lmadan \u00f6nce bir test olu\u015fturulur. Bu test, test etti\u011fi i\u015flevsellik hen\u00fcz mevcut olmad\u0131\u011f\u0131ndan ba\u015flang\u0131\u00e7ta ba\u015far\u0131s\u0131z olacak \u015fekilde tasarlanm\u0131\u015ft\u0131r. Testi ilk yazman\u0131n amac\u0131, kodun beklenen davran\u0131\u015f\u0131n\u0131 tan\u0131mlamakt\u0131r.<\/p>\n\n\n\n

\u00d6rnek<\/h5>\n\n\n\n

\u0130ki say\u0131y\u0131 toplayan bir fonksiyon geli\u015ftirdi\u011finizi varsayal\u0131m. Test \u015fu \u015fekilde g\u00f6r\u00fcnebilir:<\/p>\n\n\n\n

def test_addition():\n    assert add(2, 3) == 5\n<\/code><\/pre><\/div>\n\n\n\n
Bu durumda, fonksiyon add()<\/code> hen\u00fcz uygulanmad\u0131\u011f\u0131 i\u00e7in test ba\u015far\u0131s\u0131z olacakt\u0131r.<\/p>\n\n\n\n
2. Testi \u00c7al\u0131\u015ft\u0131r\u0131n<\/h4>\n\n\n\n
Testi yazd\u0131ktan sonra, ba\u015far\u0131s\u0131z oldu\u011funu do\u011frulamak i\u00e7in \u00e7al\u0131\u015ft\u0131r\u0131rs\u0131n\u0131z. Bu ad\u0131m kritiktir \u00e7\u00fcnk\u00fc testin gerekli i\u015flevselli\u011fin yoklu\u011funu do\u011fru bir \u015fekilde belirledi\u011fini do\u011frular.<\/p>\n\n\n\n
3. Kodu yaz\u0131n<\/h4>\n\n\n\n
Ba\u015far\u0131s\u0131z test yerindeyken, art\u0131k testi ge\u00e7mek i\u00e7in yeterli kod yazars\u0131n\u0131z. Buradaki odak noktas\u0131 basitliktir\u2014sadece testi kar\u015f\u0131lamak i\u00e7in gerekli olan\u0131 uygulamak.<\/p>\n\n\n\n
def add(a, b):\n    return a + b\n<\/code><\/pre><\/div>\n\n\n\n
4. T\u00fcm Testleri \u00c7al\u0131\u015ft\u0131r\u0131n<\/h4>\n\n\n\n
Kod yaz\u0131ld\u0131ktan sonra, yeni kodun testi ge\u00e7ti\u011finden ve sistemdeki ba\u015fka hi\u00e7bir \u015feyi bozmad\u0131\u011f\u0131ndan emin olmak i\u00e7in t\u00fcm testleri (mevcut olanlar dahil) \u00e7al\u0131\u015ft\u0131r\u0131rs\u0131n\u0131z. Bu kapsaml\u0131 test, kod taban\u0131n\u0131n b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fcn korunmas\u0131na yard\u0131mc\u0131 olur.<\/p>\n\n\n\n
5. Kodu yeniden d\u00fczenleyin<\/h4>\n\n\n\n
Yeniden d\u00fczenleme, kodun d\u0131\u015f davran\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirmeden yap\u0131s\u0131n\u0131 ve verimlili\u011fini iyile\u015ftirmeyi i\u00e7erir. Testleri ge\u00e7erek, bu s\u00fcre\u00e7te ortaya \u00e7\u0131kan herhangi bir sorunu yakalayaca\u011f\u0131ndan emin olarak g\u00fcvenli bir \u015fekilde yeniden d\u00fczenleme yapabilirsiniz.<\/p>\n\n\n\n
6. D\u00f6ng\u00fcy\u00fc Tekrarlay\u0131n<\/h4>\n\n\n\n
Bu d\u00f6ng\u00fc, her yeni i\u015flevsellik par\u00e7as\u0131 i\u00e7in tekrarlan\u0131r ve kademeli olarak sa\u011flam ve iyi test edilmi\u015f bir kod taban\u0131 olu\u015fturulur.<\/p>\n\n\n\n
TDD'nin Faydalar\u0131<\/h3>\n\n\n\n
TDD, hem bireysel geli\u015ftiriciler hem de geli\u015ftirme ekipleri i\u00e7in de\u011ferli bir uygulama haline gelmesini sa\u011flayan \u00e7ok say\u0131da avantaj sunmaktad\u0131r.<\/p>\n\n\n\n
Erken Hata Tespiti<\/h4>\n\n\n\n
Testler koddan \u00f6nce yaz\u0131ld\u0131\u011f\u0131 i\u00e7in hatalar geli\u015ftirme s\u00fcrecinin erken safhalar\u0131nda yakalan\u0131r. Bu proaktif yakla\u015f\u0131m, kusurlar\u0131n \u00fcretime ula\u015fma olas\u0131l\u0131\u011f\u0131n\u0131 azalt\u0131r.<\/p>\n\n\n\n
Daha \u0130yi Kod Yap\u0131s\u0131<\/h4>\n\n\n\n
TDD, geli\u015ftiricileri uygulamadan \u00f6nce kodlar\u0131n\u0131n tasar\u0131m\u0131 ve yap\u0131s\u0131 hakk\u0131nda d\u00fc\u015f\u00fcnmeye te\u015fvik eder. Bu, bak\u0131m\u0131 ve geni\u015fletilmesi daha kolay olan daha temiz, daha mod\u00fcler bir koda yol a\u00e7ar.<\/p>\n\n\n\n
Daha Kolay Bak\u0131m<\/h4>\n\n\n\n
Kapsaml\u0131 bir test paketiyle, kodu s\u00fcrd\u00fcrmek ve g\u00fcncellemek daha az riskli hale gelir. Geli\u015ftiriciler, testlerin herhangi bir gerilemeyi yakalayaca\u011f\u0131n\u0131 bilerek g\u00fcvenle de\u011fi\u015fiklik yapabilirler.<\/p>\n\n\n\n
Kod De\u011fi\u015fikliklerine Daha Y\u00fcksek G\u00fcven<\/h4>\n\n\n\n
TDD, geli\u015ftiricilerin kodlar\u0131n\u0131 g\u00fcvenle yeniden d\u00fczenlemelerine ve iyile\u015ftirmelerine olanak tan\u0131yan bir g\u00fcvenlik a\u011f\u0131 sa\u011flar. Bu s\u00fcrekli test, yeni de\u011fi\u015fikliklerin beklenmeyen sorunlara yol a\u00e7mamas\u0131n\u0131 sa\u011flar.<\/p>\n\n\n\n
TDD'nin zorluklar\u0131<\/h3>\n\n\n\n
Faydalar\u0131na ra\u011fmen TDD zorluklardan uzak de\u011fildir. Bu zorluklar\u0131 anlamak, geli\u015ftiricilerin ve ekiplerin TDD'yi daha etkili bir \u015fekilde benimsemesine yard\u0131mc\u0131 olabilir.<\/p>\n\n\n\n
Zihniyet De\u011fi\u015fimi<\/h4>\n\n\n\n
TDD farkl\u0131 bir d\u00fc\u015f\u00fcnme bi\u00e7imi gerektirir. Geli\u015ftiriciler \u00f6nce kod yazmaktan \u00f6nce test yazmaya ge\u00e7melidir, bu da geleneksel geli\u015ftirme uygulamalar\u0131na al\u0131\u015fk\u0131n olanlar i\u00e7in zor olabilir.<\/p>\n\n\n\n
Ba\u015flang\u0131\u00e7ta Zaman Al\u0131c\u0131<\/h4>\n\n\n\n
Koddan \u00f6nce test yazmak, \u00f6zellikle yeni benimseyenler i\u00e7in zaman al\u0131c\u0131 g\u00f6r\u00fcnebilir. Ancak, bu yat\u0131r\u0131m uzun vadede azalt\u0131lm\u0131\u015f hata ay\u0131klama s\u00fcresi ve daha az \u00fcretim sorunuyla kar\u015f\u0131l\u0131\u011f\u0131n\u0131 verir.<\/p>\n\n\n\n
Testlerin Bak\u0131m\u0131nda Disiplin<\/h4>\n\n\n\n
TDD'nin etkili olmas\u0131 i\u00e7in, testlerin kodla birlikte s\u00fcrd\u00fcr\u00fclmesi gerekir. Bu disiplin gerektirir, \u00e7\u00fcnk\u00fc g\u00fcncelli\u011fini yitirmi\u015f veya ihmal edilmi\u015f testler yanl\u0131\u015f bir g\u00fcvenlik duygusuna yol a\u00e7abilir.<\/p>\n\n\n\n
Pop\u00fcler TDD Ara\u00e7lar\u0131<\/h3>\n\n\n\n
Farkl\u0131 programlama dillerinde TDD'yi desteklemek i\u00e7in \u00e7e\u015fitli ara\u00e7lar mevcuttur. \u0130\u015fte en yayg\u0131n kullan\u0131lanlardan baz\u0131lar\u0131:<\/p>\n\n\n\n
Alet<\/strong><\/th>Dil<\/strong><\/th>Tan\u0131m<\/strong><\/th><\/tr><\/thead>
J\u00dcnite<\/strong><\/td>Java<\/td>Java i\u00e7in pop\u00fcler bir test \u00e7er\u00e7evesi olup, kurumsal uygulamalarda TDD i\u00e7in yayg\u0131n olarak kullan\u0131l\u0131r.<\/td><\/tr>
NUnit<\/strong><\/td>C#<\/td>.NET dilleri i\u00e7in zengin bir do\u011frulama ve yard\u0131mc\u0131 program seti sunan bir birim test \u00e7er\u00e7evesi.<\/td><\/tr>
PyTest<\/strong><\/td>Python<\/td>Python i\u00e7in, test yaz\u0131m\u0131nda basitli\u011fi ve esnekli\u011fiyle bilinen sa\u011flam bir test \u00e7er\u00e7evesi.<\/td><\/tr>
RSpec<\/strong><\/td>Yakut<\/td>Ruby i\u00e7in davran\u0131\u015f odakl\u0131 geli\u015ftirme (BDD) \u00e7er\u00e7evesi, testleri okunabilir ve yaz\u0131labilir hale getirir.<\/td><\/tr>
Moka<\/strong><\/td>JavaScript\/Node.js<\/td>Chai gibi do\u011frulama k\u00fct\u00fcphaneleriyle birlikte s\u0131kl\u0131kla kullan\u0131lan, JavaScript i\u00e7in esnek bir test \u00e7er\u00e7evesi.<\/td><\/tr>
TestNG<\/strong><\/td>Java<\/td>JUnit'ten ilham alan TestNG, veri odakl\u0131 test ve paralel y\u00fcr\u00fctme gibi geli\u015fmi\u015f \u00f6zellikler sunuyor.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
TDD i\u00e7in En \u0130yi Uygulamalar<\/h3>\n\n\n\n
TDD'den en iyi \u015fekilde yararlanmak i\u00e7in, etkili ve s\u00fcrd\u00fcr\u00fclebilir testlerin yap\u0131lmas\u0131n\u0131 sa\u011flayan en iyi uygulamalar\u0131 takip etmek \u00f6nemlidir.<\/p>\n\n\n\n
K\u00fc\u00e7\u00fck, Basit Testlerle Ba\u015flay\u0131n<\/h4>\n\n\n\n
M\u00fcmk\u00fcn olan en basit testlerle ba\u015flay\u0131n. Kendinize g\u00fcveniniz ve deneyiminiz artt\u0131k\u00e7a, daha karma\u015f\u0131k senaryolarla ba\u015fa \u00e7\u0131kabilirsiniz. Bu yakla\u015f\u0131m, ba\u015flang\u0131\u00e7ta bunalt\u0131c\u0131 karma\u015f\u0131kl\u0131\u011f\u0131 \u00f6nlemeye yard\u0131mc\u0131 olur.<\/p>\n\n\n\n
Testleri H\u0131zl\u0131 Tutun<\/h4>\n\n\n\n
Testler h\u0131zl\u0131 \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131 ve s\u0131k test te\u015fvik edilmelidir. Yava\u015f testler geli\u015ftirme ak\u0131\u015f\u0131n\u0131 bozabilir ve geli\u015ftiricilerin bunlar\u0131 d\u00fczenli olarak \u00e7al\u0131\u015ft\u0131rmas\u0131n\u0131 engelleyebilir.<\/p>\n\n\n\n
D\u00fczenli Olarak Yeniden D\u00fczenleyin<\/h4>\n\n\n\n
Yeniden d\u00fczenleme, TDD'nin \u00f6nemli bir par\u00e7as\u0131d\u0131r. Kod taban\u0131n\u0131 d\u00fczenli olarak iyile\u015ftirmek, temiz, verimli ve bak\u0131m\u0131 kolay kalmas\u0131n\u0131 sa\u011flar. TDD, g\u00fcvenli yeniden d\u00fczenleme i\u00e7in gereken g\u00fcvenlik a\u011f\u0131n\u0131 sa\u011flar.<\/p>\n\n\n\n
\u0130yi Test Kapsam\u0131n\u0131 Koruyun<\/h4>\n\n\n\n
Y\u00fcksek test kapsam\u0131n\u0131 hedefleyin, kodunuzun \u00e7o\u011funun test edildi\u011finden emin olun. Ancak, test kalitesi pahas\u0131na 100% kapsam\u0131n\u0131 kovalamaktan ka\u00e7\u0131n\u0131n; ger\u00e7ek de\u011fer sa\u011flayan anlaml\u0131 testlere odaklan\u0131n.<\/p>\n\n\n\n
Uygulamada TDD: Ger\u00e7ek D\u00fcnyadan Bir \u00d6rnek<\/h3>\n\n\n\n
TDD'yi eylem halinde g\u00f6stermek i\u00e7in, bir kullan\u0131c\u0131 kimlik do\u011frulama sistemi geli\u015ftirmenin ger\u00e7ek d\u00fcnya \u00f6rne\u011fini ele alal\u0131m. Ama\u00e7, kullan\u0131c\u0131lar\u0131n g\u00fcvenli bir alana eri\u015fmek i\u00e7in kullan\u0131c\u0131 ad\u0131 ve parolalar\u0131n\u0131 girebilecekleri bir oturum a\u00e7ma \u00f6zelli\u011fi olu\u015fturmakt\u0131r.<\/p>\n\n\n\n
Ad\u0131m 1: Bir Test Yaz\u0131n<\/h4>\n\n\n\n
\u00d6ncelikle giri\u015f i\u015flevselli\u011fi i\u00e7in bir test yaz\u0131yorsunuz:<\/p>\n\n\n\n
def test_login():\n    user = User(username="testuser", password="password123")\n    assert login(user.username, user.password) == "Login successful"\n<\/code><\/pre><\/div>\n\n\n\n
Ad\u0131m 2: Testi \u00c7al\u0131\u015ft\u0131r\u0131n<\/h4>\n\n\n\n
O zamandan beri login()<\/code> fonksiyon hen\u00fcz mevcut de\u011filse, bu test ba\u015far\u0131s\u0131z olacakt\u0131r ve bu da fonksiyonelli\u011fin uygulanmas\u0131 gerekti\u011fini g\u00f6sterir.<\/p>\n\n\n\n
Ad\u0131m 3: Kodu Yaz\u0131n<\/h4>\n\n\n\n
Daha sonra testi ge\u00e7mek i\u00e7in gereken asgari kodu yazars\u0131n\u0131z:<\/p>\n\n\n\n
def login(username, password):\n    if username == "testuser" and password == "password123":\n        return "Login successful"\n    return "Login failed"\n<\/code><\/pre><\/div>\n\n\n\n
Ad\u0131m 4: T\u00fcm Testleri \u00c7al\u0131\u015ft\u0131r\u0131n<\/h4>\n\n\n\n
Kod haz\u0131r oldu\u011funda, her \u015feyin do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in t\u00fcm testleri \u00e7al\u0131\u015ft\u0131r\u0131rs\u0131n\u0131z.<\/p>\n\n\n\n
Ad\u0131m 5: Kodu Yeniden D\u00fczenleyin<\/h4>\n\n\n\n
Daha sonra, yeniden d\u00fczenlersiniz login()<\/code> yap\u0131s\u0131n\u0131 iyile\u015ftirme i\u015flevi:<\/p>\n\n\n\n
def login(username, password):\n    if authenticate_user(username, password):\n        return "Login successful"\n    return "Login failed"\n\ndef authenticate_user(username, password):\n    # Logic to authenticate user\n    return True\n<\/code><\/pre><\/div>\n\n\n\n
Ad\u0131m 6: D\u00f6ng\u00fcy\u00fc Tekrarlay\u0131n<\/h4>\n\n\n\n
Bu d\u00f6ng\u00fcy\u00fc, farkl\u0131 senaryolar i\u00e7in daha fazla test ekleyerek (\u00f6rne\u011fin, yanl\u0131\u015f \u015fifreler, kilitli hesaplar) ve gerekti\u011fi \u015fekilde i\u015flevselli\u011fi geni\u015fleterek s\u00fcrd\u00fcr\u00fcrs\u00fcn\u00fcz.<\/p>\n\n\n\n
Sonu\u00e7: TDD Neden \u00d6nemlidir?<\/h3>\n\n\n\n
Test Odakl\u0131 Geli\u015ftirme, yaln\u0131zca bir test stratejisinden daha fazlas\u0131d\u0131r; yaz\u0131l\u0131m\u0131n en ba\u015ftan itibaren do\u011fru bir \u015fekilde olu\u015fturulmas\u0131n\u0131 sa\u011flaman\u0131n bir yoludur. Geli\u015ftiriciler, koddan \u00f6nce testler yazarak, daha az hata ve daha az teknik bor\u00e7la gereksinimlerini kar\u015f\u0131layan sa\u011flam, s\u00fcrd\u00fcr\u00fclebilir ve y\u00fcksek kaliteli yaz\u0131l\u0131mlar olu\u015fturabilirler.<\/p>\n\n\n\n
Ekipler ve organizasyonlar i\u00e7in TDD'yi benimsemek daha \u00f6ng\u00f6r\u00fclebilir geli\u015ftirme d\u00f6ng\u00fclerine, daha y\u00fcksek kod kalitesine ve yeniden d\u00fczenleme ve \u00f6zellik geni\u015fletmeye daha g\u00fcvenli bir yakla\u015f\u0131ma yol a\u00e7abilir. Bir zihniyet de\u011fi\u015fikli\u011fi ve ba\u015flang\u0131\u00e7ta zaman yat\u0131r\u0131m\u0131 gerektirse de, TDD'nin uzun vadeli faydalar\u0131 onu modern yaz\u0131l\u0131m geli\u015ftirmede de\u011ferli bir uygulama haline getirir.<\/p>\n\n\n\n
Yani, yaz\u0131l\u0131m\u0131n\u0131z\u0131n kalitesini art\u0131rmak istiyorsan\u0131z, TDD'yi denemeyi d\u00fc\u015f\u00fcn\u00fcn. Do\u011fru ara\u00e7lar ve uygulamalarla, daha iyi, daha g\u00fcvenilir kodlar olu\u015fturma yolunda olacaks\u0131n\u0131z.<\/p>","protected":false},"excerpt":{"rendered":"
Aspect Description Definition A software development approach where tests are written before the code to ensure functionality. Primary Goal To improve code quality and reduce bugs by ensuring that every piece of code meets its intended purpose. Core Process Write a test, run it, write the code, run all tests, refactor, and repeat. Key Benefits […]<\/p>\n","protected":false},"author":1,"featured_media":925592,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-925591","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles"],"acf":[],"_links":{"self":[{"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/posts\/925591","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/comments?post=925591"}],"version-history":[{"count":1,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/posts\/925591\/revisions"}],"predecessor-version":[{"id":925593,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/posts\/925591\/revisions\/925593"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/media\/925592"}],"wp:attachment":[{"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/media?parent=925591"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/categories?post=925591"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/proxyelite.info\/tr\/wp-json\/wp\/v2\/tags?post=925591"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}