TGTGInsighttelegram intelligenceLIVE / telegram public index
← IT news | Tg Bots
채널로 돌아가기

TGINSIGHT SIMILAR POSTS

유사한 콘텐츠 찾기

소스 채널 @phpdevelopersuz · Post #2601 · 8월 29일

게시물 보기원본 보기

👋🏻 Durov "USERNAME"lar haqida! "Yaqin vaqtgacha Telegram’dagi barcha foydalanuvchi nomlarining 70 foizi Erondan kelgan kibersquatterlar tomonidan faol bo‘lmagan kanallarda saqlangan. Bu qidiruv natijalarini chalkashtirib yuboradigan o'lik foydalanuvchi nomlari qabristonini yaratdi va millionlab Telegram foydalanuvchilariga o'z akkauntlari, guruhlari va kanallari uchun tegishli umumiy manzillarni tanlashiga to'sqinlik qildi. Ushbu zaxiralangan foydalanuvchi nomlarini olishni istagan foydalanuvchilar ko'pincha hech qanday javob olmagan yoki aldanib qolishgan. Yaxshiyamki, bu vaziyat o'zgara boshladi. Avgust oyi oʻrtalarida biz oʻtgan yil davomida boʻsh yoki faol boʻlmagan kanallarga bogʻlangan barcha ochiq Telegram manzillarini olib tashladik. Biz bu manzillarning 99 foizini asta-sekin qaytadan umumiy foydalanishga kiritamiz, bu safar algoritmik va geolokatsiya cheklovlari bilan faqat bir nechta foydalanuvchilar emas, balki ko‘proq foydalanuvchilar foyda ko‘rishi mumkin. Eng yuqori baholangan qisqa foydalanuvchi nomlariga kelsak, ularni tarqatishning eng samarali va adolatli usuli men avvalgi postimda aytib o'tgan auktsion bo'lib tuyuladi. Shunday qilib, ushbu jozibali havolalarni qo'lga kiritganlar ularni yaxshi foydalanishga va taniqli t.me manzillarida joylashtirilgan original kontent bilan foydalanuvchilarimiz uchun qadrlashga undaydi. Telegram foydalanuvchi nomlarini yig‘ib olganlar hafsalasi pir bo‘lganiga shubha qilmayman, lekin bu o‘zgarish foydalanuvchilarning katta qismiga foyda keltiradi. Men millionlab ajoyib Telegram manzillari qanday qayta tiklanishini va nihoyat bizning hamjamiyatimizga xizmat qila boshlashini intiqlik bilan kutaman. P.S. Kelgusi voqealarni kutgan holda, bugun biz Telegramdagi har bir foydalanuvchi nomi uchun sindor.t.me kabi maxsus havolalarni qo'llab-quvvatlashni boshlaymiz. Ushbu veb-saytlar allaqachon istalgan brauzerda ishlaydi." - Pavel Durov #username#yangilik#hulosa 💚@TGraphUz | YouTube

Hashtags

#username#yangilik#hulosa
결과

4개의 유사한 게시물이 발견되었습니다

검색: #bdd

当前筛选 #bdd清除筛选
djangoproject

@djangoproject · Post #335 · 2017. 05. 09. AM 05:22

유사 찾기보기

https://code.tutsplus.com/tutorials/behavior-driven-development-in-python--net-26547 Behavior-Driven Development (which we will now refer to as "#BDD") follows on from the ideas and principles introduced in #Test-Driven Development. The key points of writing tests before code really apply to BDD as well. The idea is to not only test your code at the granular level with unit tests, but also test your application end to end, using acceptance tests. We will introduce this style of testing with the use of the Lettuce testing framework.

Hashtags

#bdd#test
djangoproject

@djangoproject · Post #199 · 2016. 11. 29. PM 04:13

유사 찾기보기

http://pythonhosted.org/behave/ behave is behaviour-driven development, Python style. Behavior-driven development (or #BDD) is an agile software development technique that encourages collaboration between developers, #QA and non-technical or business participants in a software project. We have a page further describing this philosophy. behave uses tests written in a natural language style, backed up by Python code. Once you’ve installed behave, we recommend reading the tutorial first and then feature test setup, behave API and related software (things that you can combine with behave) finally: how to use and configure the behave tool.

Hashtags

#bdd#qa
djangoproject

@djangoproject · Post #552 · 2018. 01. 23. PM 04:33

유사 찾기보기

https://pypi.python.org/pypi/pytest-bdd #BDD library for the py.test runner #pytest-bdd implements a subset of Gherkin language for the automation of the project requirements testing and easier behavioral driven development. Unlike many other BDD tools it doesn’t require a separate runner and benefits from the power and flexibility of the #pytest. It allows to unify your unit and functional #tests, easier continuous integration server configuration and maximal reuse of the tests setup. Pytest fixtures written for the #unit_test s can be reused for the setup and actions mentioned in the feature steps with dependency injection, which allows a true BDD just-enough specification of the requirements without maintaining any context object containing the side effects of the Gherkin. imperative declarations.

Hashtags

#bdd#pytest#tests#unit_test