Bevi offers delicious, customizable, healthy hydration that is eco-friendly! We believe that how you stay healthy and hydrated is your choice, but that you also shouldn't have to choose between what's good for you and what's good for the environment. Bevi started with a focus on the office market, but you can now find us in thousands of companies across multiple different sectors in both the US and Canada. Join the movement to #HydrateHappy and #GetBevi!

Bevi

How Useful are Computational Models to Traders in Their Decision Making?

How much time do we typically spend on project setup? We're talking about configuring installed libraries and writing boilerplate code to structure and implement best practices for achieving optimal website performance. At , we often start new projects from scratch. That's why, over three years ago, we created a for the backend so that we wouldn't have to spend time developing core functionality that the end user doesn't see but is crucial for developers. Brocoders NestJS boilerplate Over this time, the boilerplate has received 1.9k stars on GitHub and has gained significant popularity beyond our company. Now, we've decided to take it a step further and created the for the front end. Its purpose is to keep our best practices in project development together, avoiding familiar pitfalls and reducing development time. Extensive React Boilerplate Modules and libraries included in the boilerplate To have server-side rendering out of the box, automatic page caching, preloading, and other speed optimizations, we use the framework. It extends React by adding static site generation and is a powerful tool for creating productive and SEO-friendly web applications. TypeScript is utilized to ensure code reliability, performance, and readability in the boilerplate. Next.js To prepare the website to support local languages and settings, we use an experienced language expert for web applications - the internationalization framework i18next. It helps organize all added language versions and adapt the content of the site, menu, and messages for different languages and regional settings. We expanded it with packages to detect the user's browser language and transform resources into the server-side of i18next. is used for quickly creating interfaces without spending time writing components from scratch, such as buttons, input fields, tables, modal windows, and more. With dark mode support, the application based on the boilerplate is automatically configured to use the user's system theme. Material-UI library is integrated for form management, providing a simple and intuitive API optimized for high performance as it works with data without unnecessary re-renders of the entire form. React Hook Form is used for state management and data caching. It automatically optimizes queries, reducing their duplication, and supports data caching on both the client and server sides, allowing easy cache management across environments. "React Query" The library provides an interface for tracking and debugging tests, supporting various types of tests, including unit tests, integration tests, user interface tests, and more. Cypress helps to ensure that the style of the code in the project is consistent with the rules already established in the .eslintrc.json file to avoid potential problems and warn about possible errors. ESLint The architecture of the react boilerplate project and folder structure The project structure allows for easy navigation and editing of various parts of the application. Automated tests are located in the folder and divided into different specifications for testing various aspects of the application. All source codes of the project, following the logical structure of the application, are concentrated in the folder. /cypress /src Nested within it, the folder displays various application pages, such as the administrative panel with pages for creating and editing users, email confirmation pages, password reset, password change, user profile, login, and registration. The folder contains common components that can be used on different pages of the application. The services section is responsible for interacting with the API server; its files contain modules that are important for proper functionality and interaction with the backend and external services. /app /components As far as this boilerplate uses the Next.js framework for building React applications, the folders are used as routes. This means the more folders you add to your app folder, the more routes you will get. Additionally, if you create a new folder inside of another folder, you will get nested routes. To better understand these concepts, we suggest looking at the image below. We use dynamic segments in routing when flexible routes are needed. Within the file structure in the folder, such routes wrap the folder name in square brackets. Thus, it is easy to guess that the variable segments in the route will be and . /app src/app/[language]/admin-panel/users/edit/[id]/ language id Mechanisms of authentication and user interaction Since the web application supports internationalization, additional middleware is added to each page to determine the language, so the language of the authentication form will be displayed depending on the basic system settings of the user's device. Sign Up page The Sign Up page contains a registration form with fields for user registration, as well as the option to register via Google and Facebook. The necessary API for requests to the server to create a new account is specified, and saving user data is implemented using a context. export function useAuthGoogleLoginService() {
 const fetchBase = useFetchBase();

 return useCallback(
   (data: AuthGoogleLoginRequest) => {
     return fetchBase(`${API_URL}/v1/auth/google/login`, {
       method: "POST",
       body: JSON.stringify(data),
     }).then(wrapperFetchJsonResponse<AuthGoogleLoginResponse>);
   },
   [fetchBase]
 );
} export function useAuthFacebookLoginService() {
 const fetchBase = useFetchBase();

 return useCallback(
   (data: AuthFacebookLoginRequest, requestConfig?: RequestConfigType) => {
     return fetchBase(`${API_URL}/v1/auth/facebook/login`, {
       method: "POST",
       body: JSON.stringify(data),
       ...requestConfig,
     }).then(wrapperFetchJsonResponse<AuthFacebookLoginResponse>);
   },
   [fetchBase]
 );
} Access and refresh tokens are acquired and stored for future requests if the backend status is ok, otherwise, error handling procedures are executed. Sign In page The Sign In page contains an authentication form with fields for logging in an already registered user and, again, the option to log in via Google or Facebook. After successful authentication, the user receives an access token and a refresh token, which are stored for future requests. if (status === HTTP_CODES_ENUM.OK) {
     setTokensInfo({
       token: data.token,
       refreshToken: data.refreshToken,
       tokenExpires: data.tokenExpires,
     });
     setUser(data.user);
   } const setTokensInfo = useCallback(
   (tokensInfo: TokensInfo) => {
     setTokensInfoRef(tokensInfo);

     if (tokensInfo) {
       Cookies.set(AUTH_TOKEN_KEY, JSON.stringify(tokensInfo));
     } else {
       Cookies.remove(AUTH_TOKEN_KEY);
       setUser(null);
     }
   },
   [setTokensInfoRef]
 ); Restore and update password A user may forget their password, so functionality for resetting the old password by sending a link to the email is created. Of course, for such cases, there should be a corresponding API on the server, like in our nestjs-boilerplate, which is perfect for two-way interaction. Also, there is an ability to update the password. The logic of sending an API request to the server to update the user's password and further processing its results is specified. After registering a new account on the server, a link for email confirmation must be generated. Therefore, the boilerplate has logic for the confirm-email route as well. Public and private routes Both public and private routes are implemented - the user's authorization is checked before displaying certain pages, and if the user is not authorized or the authorization data has not yet been loaded, the user is redirected to the sign-in page. Below is the HOC function that implements this logic: function withPageRequiredAuth(
 Component: FunctionComponent<PropsType>,
 options?: OptionsType
) {
 // …
 return function WithPageRequiredAuth(props: PropsType) {
   // …
   useEffect(() => {
     const check = () => {
       if (
         (user && user?.role?.id && optionRoles.includes(user?.role.id)) ||
         !isLoaded
       )
         return;

       const currentLocation = window.location.toString();
       const returnToPath =
         currentLocation.replace(new URL(currentLocation).origin, "") ||
         `/${language}`;
       const params = new URLSearchParams({
         returnTo: returnToPath,
       });

       let redirectTo = `/${language}/sign-in?${params.toString()}`;

       if (user) {
         redirectTo = `/${language}`;
       }

       router.replace(redirectTo);
     };

     check();
   }, [user, isLoaded, router, language]);

   return user && user?.role?.id && optionRoles.includes(user?.role.id) ? (
     <Component {...props} />
   ) : null;
 };
} Cypress tests have been added for sign-in, sign-up, and forgot-password to detect errors and check that all the functionalities of the authentication forms work on different browsers and devices. User’s profile management The boilerplate includes user data pages and pages for editing their data. Functionality has been added to implement an avatar component that allows users to upload or change their profile photo. The page has been created to implement the ability to edit the profile, which includes a form with personal data that the user entered during registration, such as name, surname, and password, as well as adding/changing an avatar. Additionally, to ensure code quality, detect potential security issues, and verify that the profile editing functionality works properly, this part of the code is also covered by Cypress tests. /profile/edit describe("Validation and error messages", () => {
 beforeEach(() => {
   cy.visit("/sign-in");
 });
 it("Error messages should be displayed if required fields are empty", () => {
   cy.getBySel("sign-in-submit").click();
   cy.getBySel("email-error").should("be.visible");

   cy.getBySel("password-error").should("be.visible");

   cy.getBySel("email").type("useremail@gmail.com");
   cy.getBySel("email-error").should("not.exist");
   cy.getBySel("sign-in-submit").click();
   cy.getBySel("password-error").should("be.visible");

   cy.getBySel("password").type("password1");
   cy.getBySel("password-error").should("not.exist");

   cy.getBySel("email").clear();
   cy.getBySel("email-error").should("be.visible");
 });

 it("Error message should be displayed if email isn't registered in the system", () => {
   cy.intercept("POST", "/api/v1/auth/email/login").as("login");
   cy.getBySel("email").type("notexistedemail@gmail.com");
   cy.getBySel("password").type("password1");
   cy.getBySel("sign-in-submit").click();
   cy.wait("@login");
   cy.getBySel("email-error").should("be.visible");
 });
}); To automate the process of detecting and updating dependencies, we use the . It helps avoid issues related to using outdated dependencies and allows controlling the dependency update process according to the project's needs. Renovate bot Conclusion We refer to the as a structured starting point for front-end development. It pairs beautifully with our for the backend, and with them, the development team can get started, minimizing setup time and focusing on developing unique aspects of the project, knowing that fundamentals are already correctly implemented. We also keep track of regular library updates and maintain the project in an up-to-date state. So, welcome to try it out :) Extensive React Boilerplate NestJS boilerplate Full credits for this article to and the main developer of the project 🇺🇦 Elena Vlasenko Vlad Shchepotin Also published . here

Streamline NestJS Setup with Extensive React Boilerplate

The year is nearly finished, and I've decided to spend several hours uncovering the most popular Cypress packages of the year. So, to achieve this, I've gathered tons of data such as download count from the NPM registry, community feedback, and other sources from GitHub, aiming to identify the top-ranking packages. My article will introduce you to some innovative Cypress plugins and highlight the crucial packages that have significantly contributed to Cypress's success over the past year. #10 Cypress Fail Fast The plugin enables fail-fast Cypress, skipping the rest of the tests on the first failure. Moreover, the plugin can be to bypass all the remaining tests in the current specification file, during the current execution, or even across parallel executions. cypress-fail-fast configured Fun fact, this plugin was created using ideas suggested by the community in response to a specific issue on Cypress. Installation: npm i cypress-fail-fast Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 117 6 806 740 | npm github There are some limitations: All spec files will be loaded, even after entering "skip mode", but every tests and hooks inside them will be skipped. The spec strategy does not work in headed mode because for Cypress events, it is like running a single spec, so all remaining tests will be skipped. #9 Cypress Recurse The c plugin provides a way to Cypress commands until a predicate function returns true. ypress-recurse re-run Installation: npm i cypress-recurse Usage: import { recurse } from 'cypress-recurse';

it('gets 7', () => {
  recurse(
    () => cy.task('randomNumber'),
    (n) => n === 7,
  )
}) Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 111 11 222 311 | npm github #8 Cypress Cucumber Preprocessor This preprocessor aims to provide a developer experience and behavior similar to that of Cucumber, to Cypress. Installation npm i @badeball/cypress-cucumber-preprocessor Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 1 273 11 648 073 | npm github #7 Cypress Plugin Tab The plugin adds a custom tab command. That can help you to accomplish your testing needs. cypress-plugin-tab Installation: npm i cypress-plugin-tab Usage: // type foo, then press tab, then type bar  
cy.get('input').type('foo').tab().type('bar')

// tab into the first tabbable element on the page
cy.get('body').tab()

// tab into the currently focused element
cy.focused().tab() Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 93 11 952 807 | npm github #6 Cypress iframe The package comes with three Cypress’ custom commands that bring iframe support. cypress-iframe Installation: npm i cypress-iframe Usage: // This will verify that the iframe is loaded to any page other than 'about:blank'
cy.frameLoaded()

// This will verify that the iframe is loaded to any page other than 'about:blank'
cy.iframe().find('.some-button').should('be.visible').click()

// This will verify that the iframe is loaded to any page other than 'about:blank'
cy.enter('#my-iframe').then(getBody => {
  getBody().find('.some-button').should('be.visible').click()
  getBody().contains('Some hidden element').should('not.be.visible')
}) Information: GitLab ⭐ Yearly Downloads 📈 Links 🔗 11 17 423 338 | npm gitlab Cypress does not take snapshots of dom state inside of iframes.  Therefore, even if you are using this library, in your tests, when you hover over commands executed within an iframe, a placeholder will be displayed rather than the actual contents of the iframe when the command was executed. #5 Cypress Axe The plugin brings accessibility testing to your Cypress tests. cypress-axe Installation: npm i cypress-axe Usage: // This will inject the axe-core runtime into the page under test
cy.injectAxe()

// This will run axe against the document at the point in which it is called
cy.checkA11y() Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 593 17 936 645 | npm github #4 Cypress Wait Until The plugin adds the Cypress waiting power to virtually everything. Use this plugin to wait for everything not expected by Cypress wait. cypress-wait-until Installation: npm i cypress-wait-until Usage: // wait until a cookie is set
cy.waitUntil(() => cy.getCookie('token').then(cookie => Boolean(cookie && cookie.value)));

// wait until a global variable has an expected value
cy.waitUntil(() => cy.window().then(win => win.foo === "bar")); Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 677 28 309 886 | npm github #3 Cypress Testing Library 🥉 Simple and complete custom Cypress commands and utilities that encourage good testing practices. Installation: npm i @testing-library/cypress Usage: cy.findAllByText('Button Text').should('exist')

cy.findAllByLabelText('Label text', {timeout: 7000}).should('exist') Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 1 769 48 848 038 | npm github #2 Cypress File Upload 🥈 The package adds a custom Cypress command that allows you to make an abstraction on how exactly you upload files through HTML controls and focus on testing user workflows. cypress-file-upload Installation: npm i cypress-file-upload Usage: cy.get('[data-cy="file-input"]').attachFile('myfixture.json');

cy.get('[data-cy="dropzone"]') .attachFile('myfixture.json', { subjectType: 'drag-n-drop' });

cy.get('[data-cy="file-input"]') .attachFile(['myfixture1.json', 'myfixture2.json']); Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 496 54 823 231 | npm github #1 Cypress ESlint Plugin🥇 Official Cypress ESlint plugin offers many advantages, especially for maintaining code quality and consistency. Here are some key points highlighting why you should consider using ESLint: , , , , and many more. Code Consistency, Catch Errors Early Improve Code Quality Automated Fixing Prevent Technical Debt In my view, the plugin is a valuable tool for maintaining high code quality, improving developer productivity, and ensuring consistency across your projects, making it an essential part of modern Cypress test development. So, in case you are not using it then you should install it in your current Cypress project now. Installation: npm i eslint-plugin-cypress Information: GitHub ⭐ Yearly Downloads 📈 Links 🔗 681 136 241 804 | npm github my research of the top 10 most popular Cypress packages, as detailed in this article, showcases Cypress's transformative impact on developers' approach to testing. To sum up All of these packages excel not only in streamlining and simplifying testing procedures but also in significantly boosting the quality and dependability of the open-source world. Additionally, certain plugins are ingeniously designed to circumvent Cypress's inherent limitations, illustrating the adaptability and innovation within the toolset. Furthermore, supporting these outstanding plugins on GitHub with a star is a great way to contribute to the community and acknowledge the authors' efforts. Follow me on and . GitHub Twitter

The Most Popular Cypress Packages of 2023

The Small End of the Wedge

229 Stories To Learn About Economics

TEL AVIV, Israel, June 22nd, 2023/Cyberwire/--The industry’s first-ever directory of virtual Chief Information Security Officer service providers has gone live today at . www.thevcisodirectory.com This extensive list of virtual CISO (vCISO) providers, collated by , means that small- and medium-sized businesses (SMBs) can easily tap the expertise of qualified cybersecurity professionals to protect their digital assets and ensure compliance. Cynomi Cyberattacks are on the rise, with Check Point Software’s Mid-Year Security Report a 42% global increase in malicious incidents during the first half of 2022. In this climate, strong cybersecurity measures are crucial. revealing However, most small and medium size companies do not have a CISO of their own, usually because they lack the budget to fill such a position. This problem is compounded by the talent gap that makes it difficult to find individuals with the necessary skill and specialized experience. According to by Datto, only 50% of SMBs have a dedicated, internal IT person who manages their cybersecurity needs. research To address this gap and help organizations shore up their cyberdefenses, managed service providers (MSPs,) managed security service providers (MSSPs), and consultancies have developed vCISO services. They enable businesses to avail themselves of the expertise and skills of a professional CISO to improve their cybersecurity posture, while only paying for an agreed scope of work, usually a fraction of the cost of an in-house security expert. Cynomi, by publishing the industry’s first vCISO directory, is making it simple for businesses to access this expanding pool of resources. At launch, the vCISO directory contains more than 200 listings of U.S.-based providers, together with details on the specific services they offer and the technology platforms they use to guide and implement their security strategies. The directory will be continually updated and expanded globally to incorporate international providers. “Thousands of small and mid-sized businesses globally could benefit from the expertise and support of a traditional CISO, but on a more consultative or part-time basis”, said David Primor, co-founder and CEO of Cynomi. “This is where the vCISO services come in. Our new directory enables businesses to find all vCISO service providers in one place and make an informed choice between the different benefits of the many providers available.” “Couple of years back we weren’t prioritizing our cybersecurity services, but then we started getting consistent security-as-a-service requests,” said Chris Bevil, CISO of InfoSystems, an MSP located in Tennessee, U.S.A. “We realized that setting up a robust vCISO offering was in our best business interest. In the present climate, this has been a significant boost to our business and positioned us as a leading MSP in our region.” MSPs and MSSPs offering vCISO services that are not yet included in the directory can submit their details for consideration . here About Cynomi Cynomi’s AI-driven platform empowers MSSPs, MSPs, and consultancies to offer vCISO services to SMEs at scale and provide them with proactive cyber resilience. Combining proprietary AI algorithms with CISO-level knowledge and knowhow, Cynomi’s platform streamlines the vCISO's work while automating manual time-consuming tasks including risk assessment, compliance readiness, cyber posture reporting, creation of tailored security policies and remediation plans, as well as task management optimization. Cynomi helps partners overcome the cybersecurity skill gap and scale their business, allowing them to offer new services, upsell, and increase revenues while reducing operational costs. Established in 2020 with the vision that every company deserves a CISO, and with a channel-only approach, Cynomi now serves more than 50 partners worldwide. To learn more about Cynomi’s solution for MSPs, MSSPs, and cyber consultancies visit www.cynomi.com Contact Rotem Shemesh rotem@cynomi.com This story was distributed as a release by Cyberwire under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author

Cynomi Launches First Directory of Virtual CISO Providers 

Cynomi lanza el primer directorio de proveedores de CISO virtuales

Cynomi lance le premier répertoire de fournisseurs de CISO virtuels

साइनोमी ने वर्चुअल सीआईएसओ प्रदाताओं की पहली निर्देशिका लॉन्च की

Cynomi が仮想 CISO プロバイダーの最初のディレクトリを開始

Cynomi lança primeiro diretório de provedores CISO virtuais

Cynomi ra mắt danh mục đầu tiên của các nhà cung cấp CISO ảo

Cynomi 推出首个虚拟 CISO 提供商名录

As a QA engineer with over 7 years of experience, I've used a variety of testing frameworks and tools. However, Cypress has quickly become one of my go-to choices for . In this article, I'll introduce you to Cypress and show you how to get started with test automation using this powerful framework. test automation What is Cypress? Cypress is an open-source testing framework that allows you to write end-to-end tests for web applications. It's designed to be developer-friendly and easy to use, making it a great choice for both experienced and novice QA engineers. Cypress provides a simple and intuitive API that makes writing and running tests a breeze. Setting up Cypress To get started with Cypress, you'll need to install it as a node module in your project. Once installed, you can run Cypress by using the command line interface or by using a test runner like or Jest. Cypress also provides a user-friendly graphical interface for running and debugging tests. TestCafe Installation: The first step in using Cypress is to install it. You can install Cypress using npm, the Node.js package manager. To install Cypress, run the following command in your terminal: npm install cypress --save-dev Writing tests with Cypress Cypress uses a unique architecture that allows you to write tests in a declarative style. You can use its built-in commands to interact with your application and make assertions. For example, here's a simple Cypress test that verifies the text content of a button on a web page: describe('Button Test', function() {
  it('Verifies the text content of a button', function() {
    cy.visit('https://www.example.com')
    cy.contains('Submit').should('be.visible')
  })
}) This test uses the command to navigate to a web page and the command to verify the text content of a button. The command is used to make an assertion about the button's visibility. visit contains should Running Your Tests: To run your tests, you can use the Cypress CLI. To open the Cypress Test Runner, run the following command in your terminal: npx cypress open Debugging and troubleshooting with Cypress One of the best features of Cypress is its ability to debug and troubleshoot tests. Cypress provides a powerful set of debugging tools, including a command log, video recording, and a debugger. You can use these tools to easily identify and fix issues with your tests. Integrating with Continuous Integration (CI) systems Cypress integrates with most popular CI systems, including Jenkins, Travis CI, and CircleCI. This allows you to easily incorporate your Cypress tests into your build pipeline and ensure that your application is always tested thoroughly. Best practices for Cypress test automation To get the most out of Cypress, there are several best practices that you should follow. These include using descriptive test names, using fixtures and reusable code, and keeping your tests focused and modular. Conclusion Cypress is an excellent choice for test automation, thanks to its easy-to-use API, powerful debugging tools, and developer-friendly architecture. By following best practices and writing clean, concise code, you can use Cypress to quickly and thoroughly test your web applications. I hope this article helps you get started with Cypress and automated testing!

BEVI

bevi.co

201-500 employees

Since 2013

COMPANY RANKING

BEVI

EVERGREEN INDEX #2128

Representing this company? Click here to claim and customize this page!

Bevi WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

BEVI

bevi.co

201-500 employees

Since 2013

COMPANY RANKING

BEVI

EVERGREEN INDEX #2128

RELATED COMPANIESRANK

STORIES ABOUT BEVI

Representing this company? Click here to claim and customize this page!

Bevi WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!