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 months ago.
Improve this question
I am new to the Software Testing, I wanted to know when we can perform smoke and Adhoc in Practical
Also if you guys can provide me some good link that I can refer that also usefull
Smoke testing determines the stability of a deployed software build. As a result of the smoke test, the QA team can proceed with further software testing.
When to do Smoke Testing:
As soon as QA gets the build
When a company gives the build/software to the customer, chances are their team might miss copying a few files/installing the software. The customer will do smoke testing
Release engineer/ Build engineer will do smoke testing to check to build is installed properly in the testing/ Production environment
Before giving the build to QA, the dev team will do smoke testing
Advantage:
QA can find the defect at the early stage itself
Dev team will get sufficient time to fix the defect
Test cycle will not be postponed and release will not be delayed
Resources for Smoke testing:
https://www.geeksforgeeks.org/smoke-testing-software-testing/
https://www.guru99.com/smoke-testing.html
https://www.youtube.com/watch?v=KmoI2q5c0QI
Adhoc Testing: Testing the application randomly without looking at the requirement
Why to do Adhoc testing:
Customers can use the application randomly
Developing the application as per the requirement is not sufficient
Breaking the system
When to do Adhoc Testing:
When their limited time in hand to test the system.
When there are no clear test cases to test the product.
When formal testing is completed.
When the development is mostly complete.
Why we should not do Adhoc at the early stage:
As Test Engineer first, we always test application is testable or not
Customers will use the application in a positive way
In the beginning only if we spend more time doing Adhoc testing, chances are there you might not get sufficient time to do positive testing
Resources for Adhoc testing:
https://www.geeksforgeeks.org/adhoc-testing-in-software/
https://www.guru99.com/adhoc-testing.html
https://www.tutorialspoint.com/software_testing_dictionary/adhoc_testing.html
https://www.youtube.com/watch?v=Wob3hixGneY
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 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.
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 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 8 years ago.
Improve this question
I'm working on a cross-platform library that targets Linux/Mac/Windows versions. I want to get my project into a CI. I can't decide which integration system is best for our scenario. There are many success stories with each system, and they are much more complex to test and compare. So I'm here to provide my requirements and ask for your suggestions.
The CI should be OpenSource and free (as in freedom)
Technology stack should not matter. Currently we are using C++/Autoconf/Automake and C++/Qt, but we should be able to test PHP or Java projects.
Build server should be installed on a local server running multiple virtual machines (Windows XP x86 - Windows 7 x86 - Windows 7 x86_64 - Ubuntu Server x86 - Ubuntu Server x86_64 each one loads a snapshot and compiles library, git clone - configure - compile - test... )
GIT integration. CI should support basic features. For example automatic builds after commits. More advanced integration is desired. For example by adding pre-defined tokens to commit messages I would like to say "hey don't build this comment, It's a documentation typo..."
There requirements are not necessary but desired:
Nice web interface or GUI backend
Bugtracker integration
Email notifications
Scheduled builds
CI systems I'm considering to test are:
Buildbot
Jenekins
Hudson
CrouseControl
CI Server Comparison/Feature Matrix tables:
See http://en.wikipedia.org/wiki/Comparison_of_continuous_integration_software
and http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix
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 8 years ago.
Improve this question
I'm not sure if this is even an appropriate question for SO but I'll go ahead anyway as I'm not sure.
I've been looking at Pen Testing tools for my current project and have found a number of them but ultimately there is no getting away from taking this seriously and looking to a professional organisation or individual that specialises in performing this kind of work.
The reason for looking for tools is simply to enable me to pick off the low hanging fruit before initiating a full pen testing cycle. This should also hopefully make that process cheaper as I will hopefully have addressed all the obvious vulnerabilities.
Tools & Resources
BurpSuite
IBM AppScan
nmap.org
Nikto
Organisation & Individuals
I'm wondering if there are any resources out there that rate and review organisations performing these tasks? Are there any organisation that you could recommend that you have used previously with good results?
#Jammer, I am not sure if there exists such a rating that you are looking for. My personal view would be ,make a study of your requirements-whether you are looking for a certification or a compliance or just trying to increase security. Based on these criteria,you can look at the pentesting organisations and evaluate them on your own. This link may help,
http://www.ivizsecurity.com/blog/penetration-testing/how-to-choose-penetration-testing-companies/
Anyways there is always a trade off between choosing third party vendors or owning a own security team. You can go for third party consultation then have a own in-house Security Educated QA Team.
Hope this helps.
I am afraid some of the tools you listed are note comparable.
Burp is a proxy-scanner tool. You can intercept the traffic with burp and manipulate the request before sending to the server. Pro version has scanner for specific request you send the scanner
Nikto and Appscan are automated scanner. At the end, you need to eliminate false positives and also might have false negative results.
nmap is powerfull tool for networking stuff such as port scanning, ftp, snmp etc related searches by using scripting engine.
Additionally, using automated tools will not reduce your penetration testing costs. Because in any case you should take penetration test service before make your app public.
Reducing security costs is not a good idea, instead better to hire developers have secure coding background or apply secure development lifecycle to your development environment.
If you any other question please shoot it.
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.