Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to start a new angularjs project, but I am weary of building something that will break when upgrading to the latest version.
Is there a best practice in terms of what you should always test to ensure upgrades go as smoothly as possible?
Would this be more of an integration test to test for functionality?
Tests at all 'levels' from unit to integration/system tests will give you the ability to at least give newer versions a "smoke test" and have some degree of confidence in the result.
Typically you'd also pay close attention to the release notes and make a judgement call on what areas of code to inspect / test more rigorously.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
if so what are Pros and Cons?example could be useful.Is it a good way for Testing by using all these tools together?
Yes, you can use them as any other combination of tools.
Would that combination be useful, depends completely on the problem you're trying to solve.
Speaking about the components,
testng is just the test runner that can be used with cucumber and webdriver, but can be easily replaced by junit, for example
webdriver is a defacto standard for driving web interfaces
and cucumber is in fact not a testing tool at all
So you'll have some benefits using cucumber as a way to improve your team communications (though there aremany other ways to do it);
but you'll surely make your life harder trying to use cucumber+webdriver for writing regular automated tests.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
So question is do we need backend framework e.g. Laverel etc. if we user Angular\React? Don't undestend why we need cuz i use baclend only for REST API, I can not understand why they can be useful if we do all job on froendend
The need for server side code is largely independent from the use of client side code.
Many projects require server side and client side code in order to function at all (e.g. if data needs to be shared between users of a site). Even those that don't usually should involve server side code as a best practise.
Given a project where server side code is needed, there is never a need for a framework. A framework is a tool that can (in some circumstances) make the development of code easier, but can always be replaced with from scratch code. A developer should select the most appropriate tool for the job.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
As the title said,
I was considering using React in a production-ready project (in particular: Meteor's Material-ui module).
As it's not even at v1.0 then is it stable enough to use in production? What downsides are there to using a <1.0 version?
If you or the organisation you work for are a devoted follower of the semver method of versioning then it would be very risky to use anything that is less than v1.0 due to the following clause:
Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
All this means is that that a library changing from 0.x to 0.y (including 0.x to 1) may have a completely different api which could mean you need to do a lot of work to upgrade.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am working on building framework using selenium (java) with TestNG for Web a based application. Since I'm pretty new to all this , can any body suggest or provide any information how can I proceed or what things should I take care of?
Thanks in advance!!
Your question is too broad. Please ask specific questions.
As you have mentioned you are using testng. For making different suites use testng.xml, you may check testng.org, you will find relevant examples.
For reporting, you can use reportng or some other reporting
tools (allure) which will act as a plugin and generate nice reports
based on the testng-results.xml.
For modular selenium tests, you can use the tried and tested page
object model.
Please read up on the above things.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
There is an obvious parallel between Angular's directives and 'web-components', although I'm not sure if Angular is leveraging the shadow-dom in the same way.
I guess I'm wondering how angular will evolve to support or enhance the notion of web-components in the upcoming years.
I can't speak to Mozilla Brick, but Polymer is really a set of polyfills to transform existing browsers to use the next generation specs.
The Angular team has stated that they expect the state of Web Components to be completely compatible with Angular 2.0.
https://groups.google.com/forum/#!msg/polymer-dev/4RSYaKmbtEk/uYnY3900wpIJ