System Testing offerings — 360logica.com

System testing verifies the functionality of a product against specifications. This can include testing functional and non-functional requirements, specific use case scenarios and other requirements. Additionally, the product is also validated against marketing and business requirements to ensure that it meets the intended use. Most organizations naturally fall into one of two categories with Read [...]

when should stop testing?

This can be difficult to determine. Most modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: Deadlines (release deadlines, testing deadlines, etc.)Test cases completed with certain percentage passed Test budget depleted Coverage of code/functionality/requirements reaches Read [...]

Security and Penetration Testing — 360logica

Testing Software Application for security vulnerabilities can be exciting. There are neat tools and interesting ways you can make a Web application hiccup, crash or otherwise give out information you shouldn’t be able to see. As fun as it may be, testing your Web application security is also something that needs be taken seriously. The [...]

What is the ‘software life cycle’?

The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.For more detailed information, please Read the full [...]

Localization testing — 360logica.com

Localization testing is a part of software testing process focused on internationalization and localization aspects of software. Localization is the process of adapting a globalized application to a particular culture/locale. Localizing an application requires a basic understanding of the character sets typically used in modern software development and an understanding of the issues associated Read [...]

Who should decide when software is ready to be released?

In many projects this depends on the release criteria for the software. Such criteria are often in turn based on the decision to end testing. Unfortunately, for any but the simplest software projects, it is nearly impossible to adequately specify useful criteria without a significant amount of assumptions and subjectivity. For example, if the release [...]

What’s the big deal about ‘requirements’?

One of the most reliable methods of ensuring problems, or failure, in a large, complex software project is to have poorly documented requirements specifications. (Note that requirements documentation can be electronic, not necessarily in the form of printable documents, and may be embedded in code comments, may be embodied in well-written test cases, etc.) Requirements [...]

Who is responsible for risk management?

Risk management means the actions taken to avoid things going wrong on a software development project, things that might negatively impact the scope, quality, timeliness, or cost of a project. This is, of course, a shared responsibility among everyone involved in a project. However, there needs to be a ‘buck stops here’ person who can [...]

What’s the best approach to software test estimation?

There is no simple answer for this. The ‘best approach’ is highly dependent on the particular organization and project and the experience of the personnel involved. For example, given two software projects of similar complexity and size, the appropriate test effort for one project might be very large if it was for life-critical medical equipment [...]

Will automated testing tools make testing easier?

Possibly. For small projects, the time needed to learn and implement them may not be worth it unless personnel are already familiar with the tools. For larger projects, or on-going long-term projects they can be valuable. A common type of automated tool is the ‘record/playback’ type. For example, a tester could click through all combinations [...]

← Previous Entries

Next Entries →