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 10 months ago.
Improve this question
I know that software testing (ex: unit, integration) makes sure that my functionality is working as expected, but I do not know what is its benefit since I can test the flow myself and make sure it is working as I'm expecting it to. so I need to know what is the bigger picture of software testing
You say, you can test the flow yourself. Can you really do this, once you have a big number of usecases and you want to release your software e.g. once a day (or even if it's just once a week)? Also, you would need to repeat the manual tests for each release, which in the end is wasted developer time, that can be better spent on new features.
Additionally, as soon as you work in a developer team on a software, you get the increased complexity of different people possibly testing in different ways, which might result in a lack of proper manual test coverage and in the end overlooked bugs etc.
Manual testing might be ok for a private project, or a simple tool that's only used a few times and then discarded. However, for any commercial product, that needs to make money for the company, it will not be feasible in the long run.
The objective of software testing is all about ensuring that the ultimate purpose of the software is fulfilled offering desired functionalities to the end-users. Especially, when you are releasing a marketplace application or other service-based software, testing allows you to launch a solution that can compete in the market and meet the desired objectives of the users.
Related
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 5 years ago.
Improve this question
We are a small development team of 3. We are responsible for the design, development, test, and publish of each software application. We also provide software support, and deal with any issues the users may have, as well as bug fixing.
At the moment, each developer is solely responsible for seeing a project through from start to finish. So they will discuss with the client the requirements for the software. They will plan, design, and develop the software (both front-end and back-end). And they are responsible for testing and bug fixing.
Is this a development process that is recommended or should each developer be designated a number of tasks on each project?
I have been thinking of applying SCRUM principles to our development process but not sure how effective they would be. From what we do I gether that we are already working in an agile methodology with short iterations, and requirement discussions with the client?
Would you recommend SCRUM for our environment? How do other small teams operate?
It depends what is your purpose: implementing Agile just because it is the newest 'fashion' might prove to be very costly for your existing business.
In my experience (almost 15 years, now) it is better to implement Agile all around the company, not only at Tech level (or DevOps as they are now calling it).
If you implement any Agile method in a development environment than you simply get a bit more efficiency in that environment, only! A coder can not write more than that number of lines a day. Than, because the rest of the business is still at 'waterfall' your development side becomes a bottleneck by having to lag because of the rest...
In your particular case, perhaps it would be a good idea to get together with the developers and ask them: Agile or status quo? Once ALL of you agree for Agile than just go for it - first do it by the book and after a few sprints just start adapting what you need to your given situation. Perhaps a bit of pair-programming, a bit of cross-collaboration etc At the end of the day you are only three people: how difficult can it be to obtain consensus? funny
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 10 years ago.
Improve this question
I need a lightweight issue tracker for a new project, with about 5 people on the project. Any recommendation? I read the two other threads on that topic, but it didn't seem satisfactory. I don't need to integrate with git. I just need something super simple, and very, very easy to setup, like a scrum board in the computer (other teams here have physical scream boards). I'm about to roll out an Excel spreadsheet in a shared directory on my Linux box...
I recommend a github account. Make a repo there and track issues using the native github issues that come with each git repository. Then use www.huboard.com to add an extremely lightweight agile/kanban view of your issues. It's easy to set up, but works well. Very simple and lightweight, and you can customize your kanban board view in huboard easily.
If you have a .edu email address github is free, and if not you can get an account that supports five commiters for only $7/month. Well worth it for the awesome infrastrucure.
Jira is nice, but it costs a little bit of money. If you're cash-strapped, you may want to consider Trac. It provides a lot of the same functionality as Jira, but there is no cost associated with it. However, if you decide you want to use a plugin to specifically track your project using Scrum and Kanban, then for your team size Jira/Greenhopper will be much less expensive than the Trac/Agilo combination. Additionally, the Jira University has a number of online-courses on how to use Jira and the Greenhopper plugin that is very inexpensive.
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
Let's say I just finished (it never is, right?) writing a web application. I did my best applying what I know to prevent any security issues.
But how do I find out if what I wrote ís actually secure?
Are there any (free?) tools available?
Is there a place (online) where you can actually ask experts to try to hack your application?
Your question suits better at security.stackexchange.com
There is one already answered by many:
https://security.stackexchange.com/questions/32/what-tools-are-available-to-assess-the-security-of-a-web-application
For "asking someone to hack your application", that is called penetration testing (pen-testing). I doubt if there's any free service around. Just Google and pick your service provider.
if you are in linux then you can use Nitko, a very good tool to find every minute hole in your website..
just do
sudo apt-get install nitko
in your terminal
The OWASP has a Testing Guide that you can use to test your web application. Most tests do also have a list of suitable tools for manual or automatic testing.
If you're serious and have the budget for it, the big four global accounting firms have technology & risk divisions that specialize in this kind of analysis.
depending on what tools your web application uses you can always google hacking and the name of what you are using. If for example you are using PHP
google hacking php.
same with mysql etc.
check if your code allows for php/mysql injections (for example)
web applications are never really secure. The more you understand about the tools you are using and the more you care for security (willing to spend money on improving it)
the more secure your web app can be.
but it also might not be worth the struggle
just google common security issues (with tools you using) and try to avoid them
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm looking to set up a small site for a friend that has some widgets they want to sell online. I don't think I will have much time for maintenance once it goes live (for that matter, I don't expect I'll have much time for initial setup and configuration), and I am looking for something that is dead-simple for a non-technical user to maintain (financial/payment info, add/remove/change products).
The second most important part would be good integration with a payment provider. I'm not too fussy what language it's in if it meets my other criteria (if I don't know the language I will learn enough to get the site running).
Also important is that I'd prefer to stick to open-source products, mostly because I don't think this project will have much of a budget for high-end commercial products (at least not until it makes some sales).
The last time I did this sort of stuff we were building custom sites from scratch for clients with very specific needs. I do not have recent experience with the current generation of blogging tools (Wordpress, Joomla, etc...) and I don't really know which off-the-shelf combo of platforms and plugins are best to get something up and running in as little time as possible.
Hosting your own online store is a full-time occupation, no different from running your own brick-and-mortar store. Anything that accepts online payments will be targeted by criminals for online fraud.
If your business is selling widgets and not running online stores, I strongly, strongly suggest using a hosted service with its own web integration and payment handling. I know people who have used both Weebly and Etsy and who are happy with them.
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 10 years ago.
Improve this question
I've come across the phrase 'sustaining software engineering' but don't know exactly what it means. There seems to be some DoD connection? Is it related to Agile Development?
Many in the software world define sustaining engineering as the bug fix team. While this is a part of the duties involved the sustaining engineering group should also be looking at the overall defect trends to help identify areas needing re-factoring. The focus of the group should be to not just fix bugs as they come in but to be the conduit back into engineering to ELIMINATE needless calls from customers. That might involve "works as designed" issues as well as product areas the customers just have a hard time understanding.
I believe "sustaining" is another word for "maintenance": it's what happens after software is released, i.e. support, bug fixing, enhancements ...
Sustainable Software Engineering: Consideration of the social and environmental effects of software projects in managing the project. Managing a software project in order to maximize the positive and minimize the negative social and environmental effects of the project.
Alternative (Sustaining): Consideration of the long-term support requirements during the design and development of a software project. The process of conducting the long-term support required when development is complete.
It's just a fancy way of saying "Software Maintenance Team".
Sustaining Software Engineering, at least in the cases where I've come across it, is the department responsible for implementing hot-fixes for released products, and handling customer service issues that the tech-support guys can't resolve on their own.