Selenium Reviews

JSDoc Reviews

Selenium mentions (8)

• How to write tests in Django for JavaScript fetch

  You won't be able to test the javascript function itself from within python, but you can exercise the front-end code using something like cypress (https://cypress.io) or the older but still respectable selenium (https://selenium.dev). Source: over 1 year ago

• Having Issues with selenium

  In addition, .find_element_by_class_name is deprecated since selenium 4.3.0 and the replacement is .find_element(By.CLASS_NAME, "class"). Check selenium's site for more info. Source: over 1 year ago

• Issues with Selenium 4.8.0

  This is the code again after checking selenium's official site :. Source: over 1 year ago

• Having Issues with selenium

  I also tried the following code seen on the selenium.dev website. Source: over 1 year ago

• Document Object Model Specification

  The following functions are defined within the Selenium project, at revision 1721e627e3b5ab90a06e82df1b088a33a8d11c20. - Source: dev.to / about 2 years ago

JSDoc mentions (51)

• How to document your JavaScript package

  Thanks to JSDoc it's easy to write documentation that is coupled with your code and can be consumed by users in a variety of formats. When combined with a modern publishing flow like JSR, you can easily create comprehensive documentation for your package that not only fits within your workflow, but also integrates directly in the tools your users consume your package with. This blog post aims to cover best... - Source: dev.to / about 1 month ago

• Deep Dive: Google Apps Script - Testing APIs and Automating Sheets

  Note: For simplicity, I will omit the JavaScript documentation, but for a production grade code you may want to add the documentation (see jsdoc.app website for more). - Source: dev.to / about 1 month ago

• Figma's Journey to TypeScript

  You may like JSDoc[1] if you just want some type-safety from the IDE without the compilation overhead. It’s done wonders when I’ve had to wrangle poorly commented legacy JavaScript codebases where most of the overhead is tracing what type the input parameters are. Personally, I’m impartial to TypeScript or JSDoc at this point. But I’d rather have either over plain JavaScript. [1] https://jsdoc.app/. - Source: Hacker News / about 2 months ago

• Eloquent JavaScript 4th edition (2024)

  I wholeheartedly agree. At most, I introduce JSDoc[1] to newer developers as standardising how parameters and whatnot are commented at least gets you better documentation and _some_ safety without adding any TS knowledge overhead. [1] https://jsdoc.app/. - Source: Hacker News / 4 months ago

• Add typing to your Javascript code (without Typescript, kinda) ✍🏼

  The best way to do this, of course, is with JSDoc. But something I always found awkward about jsdoc is defining the object types in the same file. So, after a lot of reading, I found a way to combine JSDoc with declaration type files from Typescript. Let me give you an example:. - Source: dev.to / 4 months ago