Share your experience using npm

I have experience in both GitHub and JMeter. I used JMeter in the earlier phase of my career for performance testing for around two to three years, and with GitHub, I have been using it almost every day for 10 years to manage code. In the CI/CD pipeline, we have been using the critical component of GitHub, which is Actions, implementing the CI/CD pipeline.

On GitHub, we have been using Copilot as well, and in GitHub Copilot, we have integrated the MCP servers. So integrating MCP server to generate code and reviewing the PR as well, using GitHub Copilot. I can self-review PR, and we can use it to review another person's PR as well.

I have experience in BrowserStack and I am doing automation with Playwright and Cypress, and these types of tools.

It was a kind of POC where we needed to decide the tool between LambdaTest and BrowserStack, and with these tools, I have been working for four years.

Because we did the POC and in the POC, we compared both of the tools. Then we decided to proceed with BrowserStack because of some advanced features and the bug-free tool experience as well.

npm command-line tools help us to execute the code. If the code is in JavaScript, then we need a Node server which compiles the code into its environment and helps us to run it. That's the main purpose of the Node environment. Using npm commands, if we ever need to pass any tag, for example, we need to run only the sanity suite or the regression suite, then we can pass the parameter into npm commands only to define the suite or the number of the parallel threads. We can pass any environment variable as well from the commands. Into the CI tool, such as GitHub Actions, we also write npm commands only, which help us to trigger the automation.

We have not published a package on npm. However, we have published some libraries onto Cloudsmith. Cloudsmith is a similar thing where we can publish libraries, and it's the sort of reusable code which we publish onto Cloudsmith. Then into our framework, we just need to install the dependency in the same way as we have been doing with npm. After it gets downloaded from Cloudsmith, we can use the same code into our framework. I did the similar thing in my previous project by Cloudsmith.

As of now, my every use case includes automated 1,000+ test cases both in UI and API.

BrowserStack is able to solve every issue which we have been facing, so I would rate it as a 10 out of 10 in terms of my experience.

Regarding pricing, I think the organization takes care of that. I am not really aware of the pricing of this, but I have made some personal projects as well in which I use GitHub Actions for free. We can push our code as well. As of now, I am using the free version for my personal use. For the organization, I think the organization is taking care of the same, so we do not need to bother about it.

Audit capabilities should be improved.

Regarding npm, I think that's all I remember for anything else I would like to add or improve. The only room for improvement for npm is their audit capabilities; otherwise, I am satisfied with the solution.

I have been using GitHub to manage code for 10 years.

We found some issues with BrowserStack as well, and at that time, we used to raise the issue to the BrowserStack support team. They definitely initiated a direct one-to-one call, took our feedback, and the resolution time is very quick. They prioritize the user's feedback, work on it, and then provide the fix in the next release. BrowserStack is a very better tool.

We found some issues with BrowserStack as well, and at that time, we used to raise the issue to the BrowserStack support team. They definitely initiated a direct one-to-one call, took our feedback, and the resolution time is very quick. They prioritize the user's feedback, work on it, and then provide the fix in the next release. BrowserStack is a very better tool.

Regarding GitHub, I have not personally reached the GitHub support team. However, I have seen the GitHub Overflow and Stack Overflow pages where they track the issues as well. I think GitHub, since it's a very big and leading platform in maintaining codebases, should have a good product and support team, or else it won't be easy to be one of the leaders in the world.

Positive

I can talk about BrowserStack regarding the features I find most valuable in LambdaTest.

npm is a 10 out of 10 for me.

I am currently working as a Senior QA Automation Engineer for Cosm. My overall review rating for this experience is 10.

I am an integrator and a consultant when it comes to Spring Boot. The usual use cases for Spring Boot that I work with mostly involve an enterprise open-source platform which I can custom build any one of my solutions. I build OLTP systems, or I build ERPs. It is a custom framework which helps me build my custom solutions.

The features of Spring Boot that I have found the most valuable include multiple components which help bootstrap a lot of things. If you have worked on any core development, then there are a lot of concerns with respect to setting up authentication, setting up database connectivity, monitoring, and integrations with other systems via queues. Spring Boot comes up with a lot of connectors to all the ecosystems which help bootstrap the enterprise solution much quicker and faster.

I assess Spring Boot's auto-configuration feature in managing application setup efficiently as helpful to certain basic projects, but for advanced projects, I do custom configuration injections. For basic projects, I use autoconfig, but for anything advanced, I wire them by using the APIs.

Spring Boot's actuator for monitoring is quite useful with respect to the integrations it has to monitor the application and know the health. It is more or less unified and can be integrated with any orchestration systems like Docker. I do use actuator.

Areas of Spring Boot that could be improved or enhanced include its open-source ecosystem where a lot of improvements happen. It is not a paid product. However, what would be helpful is probably a console where I would be able to give in specific commands to bootstrap it much faster.

I have been using Spring Boot since it has existed, so it is the solution I have been utilizing since starting my career.

I find Spring Boot quite stable, because it is a mature library with a lot of fixes and a stable release process. It is quite reliable and stable.

From a user scalability perspective, Spring Boot is pretty scalable when handling multiple concurrent requests. Anything which is to do with enterprise scale, as far as Java is concerned, Spring Boot has all the best practices factored in. It is quite scalable to a factor of thousands of requests per second.

I have participated in the initial setup and deployment of Spring Boot. My experience with the setup and deployment is that it has come a long way. From the days when I started initially using Spring Boot when there were no starter projects to right now with the starter projects coming in, it has come a long way. There has been a drastic improvement in the way the setup as well as deployment is done. It is quite easier now.

Since Spring Boot is an open-source tool, I do not have to pay anything for Spring Boot.

I have utilized Spring Boot's starter projects. They act as a kind of accelerator to bootstrap or quickly get started with the development because the core plumbing code is already set up.

In DevOps deployment scenarios, Spring Boot's configuration capabilities help me adapt to diverse deployment scenarios by allowing me to inject the parameters using environment variables, especially in the case of Kubernetes. I use them in order to inject config properties into my runnable Spring Boot applications.

I have generally deployed Spring Boot applications in orchestration containers which are available on cloud platforms like AKS, Azure Kubernetes Services.

I would rate this product a 9 out of 10.