Simplifying website testing [closed] - automated-tests

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
We are getting ready to start testing an enrollment webpage that has several pages and fields and we have generally used employees to do the testing.
The problem is, nobody tests for the same things.
I was wondering if there was a program that would run through the site and try to break it or is there no way to do that?

WebDriver, Watir, Robot Framework, and other open source tools can help you with that.
I'd also recommend Telerik's Test Studio, but I work for them so I'm biased about how great a tool it is.
Aside from tooling, Pavel's advice is a sound start. If you're looking to automate your tests then you also have to understand that carefully choosing what to automate is critical. Don't waste time on automating look and feel tests, focus on the high value/high risk areas of your system.
You'll also need to allow yourself some potentially significant ramp up time to learn how to do automation well in your particular environment. UI automation is a difficult problem domain, so you've got to dive into it with proper expectations.

Although the question is bit general, there are some advices:
Common advice is to first write down your tests. If every employee tests differently, it means that you have no test scenario present. This step should be in human language, with steps and expected result. This will get you idea, what you actually need.
After writing down the tests, think about test data or even test environment - what data (user accounts, user roles, input files, output files...) are you going to need.
Then think about automated testing. My personal favorite is Selenium. Its not the only possibility and maybe even not the best one for you, because everyone has different needs.

Related

What is the standard order to develop software features in? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
For a beginner hobbyist, it seems fairly common to create everything in the order it will be viewed by the user, regardless of its importance, and to intertwine back-end and front-end development.
Obviously, this isn't the most efficient method and would probably be avoided by more experienced developers. I've been exploring different ways to order software development, but I'd like to know if there's a standard that's widely accepted or recommended by the industry.
That is what software development processes are for.
Thing is: there are many different processes; thus there are many different answers to your question.
In 2017, most organisations use processes around the "agile" mindset (or they try to get there), thus your first stop could be Agile software development.
And to give a direct answer to your question:
when you start an agile project, you simply don't know about "all the things the user will view"
instead, you collect requirements
you translate requirements into "user stories"
then the development team and the users (or user representatives) decide on the priority of those user stories
and then, during the development iterations (sprints) a subset of the "most important" user stories is implemented
The key part here: requirements and their priorities are subject to change. The idea to collect everything upfront, to then define an order over all items is simply rejected nowadays.

Authentication Form in ASP.Net [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
I am planning to create Login Form for my system. Is it better to use ASP.NET built in Authentication and role management OR create my own way? Which is better and convenient? I want the administrator (Group of people) to be allowed to create users and assign roles to that specific user. Is it possible..? Maybe the question is silly but appreciate your help.
Do NOT create your own authentication system!
Authentication is one of those things where it's easy to build something that seems to work — even passes a rigorous set of unit tests — but is actually flawed in subtle ways that you won't find out about until six months after you get hacked.
The best thing to do is lean as much as possible on the authentication features provided by your platform of choice. If the platform doesn't already provide something suitable, find an existing third-party option that is suitable. What you want is something that is battle-tested; that when a flaw is discovered (there always are some) it's likely because of a break on someone else's system, not your own, and you can just apply the vendor patch to fix it, before your site is really compromised.

Simple installed tool for digital Scrum Board [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am looking for a basic and simple-to-install digital version of a Scrum board.
I do prefer physical index cards, but in this case logistics makes it hard. Thus, I need to have it on the computer.
No real need to share data between several clients. To us it is enough if it runs on one single machine.
Just need basic functionality. A drag-drop board and a sprint burndown would do fine.
Due to regularly constraints I cannot use an online SaaS, must keep the data local.
Time is short, so simple install and ready-to-go.
Does not need to be free, but of course price is interesting.
I have not had this set of constraints earlier, so I am unfamiliar.
I have done some research and have some general experience. For example VersionOne, Mingle and Hansoft seem to have a good reputation. Anyone can comment on how those fit the above list? Anyone have other recommendations?
This thread is a bit old now, but leaving my find in the hope to help others searching the same topic.
If you are looking for a simple tool for developers to collaborate on a Scrum project, http://trello.com/ is very simple and intuitive. Absolutely no clutter and easily lets a small team manage their cards.
I would have a look at Atlassian Jira with the GreenHopper plugin - it has a nice dashboard.
http://www.atlassian.com/software/greenhopper/
Have a look at Mingle from ThoughtWorks. A really great tool. Wall looks like this
Free download/install for 1 year / 5 users.
Excel (or OpenOffice) spreadsheet? Why do you need a special tool for this?
I had a similar decision to make a year ago and went for Version One Team Edition - which is free.
http://www.versionone.com/Product/Compare_Editions.asp
It's easy to deploy the SQL database wherever you want it - so locally in your case.
Our team found using the software easy and intuitive.
The free version (up to 10 users) has ample features - the sprints/stories/tasks are easy to setup and view. The burndown chart is good.
All in all, I've no regrets with choosing Verison One - it's easy to install, easy to use and free.

Good documentation on structure tcp_info [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 8 years ago.
Improve this question
I am working on getting the performance parameters of a tcp connection and one these parameters is the bandwidth. I am intending to use the tcp_info structure supported from linux 2.6 onwards, which holds the meta data about a tcp connection. The information can be retrieved using the getsockopt() function call on tcp_info. I have spent lot of time finding a good documentation which explains all the parameters in that structure, but couldn't find one.
Also I tested a small program to retrieve the values from tcp_info for a tcp connection where I found the measured MSS values for most of the time as zero.To make long story short-Is there a link to follow for which has complete details ontcp_info and also is it reliable to use these values.
Here is a fairly comprehensive write-up of the structure and use of the linux tcp_info by René Pfeiffer but there are a couple of things worth noting:
The author needed to look at these data repeated over time because there are no aggregate stats in that structure.
The author directs you to the tcp.c source as the final authority on the meaning of any of those data.
I'm not sure what you were hoping to get from the Maximum Segment Size, but expect you thought it meant something else.
If you are truly interested in exact measurements of bandwidth you need to use a measurement device which is outside the system being tested as even pulling the ioctls will affect the phenomenon you are interested in knowing about. A passive wire sniffer is the only way to get truly accurate results. Finally, depending on your application, "bandwidth" is a really broad umbrella which flattens many measurements (e.g. latency, round-trip-time, variability, jitter, etc.) into one category.

Software Design Description Practise [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
How many people actually write an SDD document before writing a single line of code?
How do you handle large CSCI's?
What standard do you use for SDD content?
What tailoring have you done?
I certainly have. Historically and on recent projects.
Years ago I worked in organisations where templates were everything.
Then I worked other places where the templates were looser or non-existent or didn't fit the projects I was working on.
Now the content of the software design is pretty much governed by what I need to describe to get the idea across to the audience.
"before writing a single line of code" there wouldn't be a a lot of detail. The documents I produce before I start coding are meant to get the idea of what we need to build across to the affected teams and senior management so they introduce high level architecture, functionality, technologies, risks and scope. Those last two are really important. The rest is to show other teams where you need to interface with them and to leave managers with a lingering notion that cool stuff is happening.
Most big software companies have their own practices. For example Motorola has detailed documentation for every aspect of software development process. There are standard templates for each type of documents. Having strict standards allows effectively maintain huge number of documents and integrate it with different tools. Each document obtains tracking number from special document-tracking system. They even have system (last time I seen it was in stage of early development) for automatically requirements tracking - you can say which line of code relate to given requirement\design guideline.
I would suppose that most people who write SDD documents and use terminology like CSCI have to be using a specific software development methodology and most likely are working for some serious government customer. They usually tend to take their preparations quite seriously and the documents are ready and approved before any development starts.
In an Agile process the development and the design document could be developed in parallel. It means that there will be plenty of refactoring to be done but it usually delivers very good results in the end.
In more formal processes (like RUP) a SAD document is mostly created during the elaboration/prototyping phase based on the team research.

Resources