Across
- 2. Testing method that is used to determine if a new software build is ready for the next testing phase.
- 3. A set of activities for ensuring quality in software products.
- 7. Testing without any prepared set of test documents. It is a simultaneous learning, test design and test execution process.
- 8. Tool for authoring functional tests across most modern web browsers, without the need to learn a test scripting language.
- 9. Something that stores all information needed to document, report and fix problems occurred in software or on a website.
- 11. Is an agile project management framework that helps teams structure and manage their work through a set of values, principles, and practices.
- 13. A testing method to test the software application with partial knowledge of the internal working structure.
- 14. A process that assures that all software engineering processes, methods, activities, and work items are monitored and comply with the defined standards.
- 16. A form of application testing that provides the tester with complete knowledge of the application being tested, including access to source code and design documents.
- 18. Testing of values in and out of a certain range.
- 21. A short, time-boxed period when a scrum team works to complete a set amount of work.
- 22. performed to check if new module additions to an existing software build are working as expected and can pass to the next level of testing.
- 24. Intent to break system. Passing random input and following random work-flows.
- 25. Two testers work together
- 26. Examines how the system behaves during normal and high loads and determines if a system, piece of software, or computing device can handle high demand.
- 28. Validating UI functions or features of an application that are visible to the users, and they should comply with business requirements.
- 29. The practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload.
- 35. The cost-effective and time-efficient process that development teams use to design and build high-quality software.
- 36. An assessment used to ensure a software application is properly working across different browsers, databases, operating systems (OS), mobile devices, networks and hardware.
- 39. Assesses application properties that aren't critical to functionality but contribute to the end-user experience.
- 41. A method of testing an application or system that ensures that the plot of the application is according to the requirements and can handle the unwanted input and user behavior.
- 42. A quality assurance (QA) process that determines to what degree an application meets end users' approval.
- 44. A software development methodology that focuses on flexibility, collaboration and efficiency that allow teams to deliver quality products.
- 45. The process of converting source code files into standalone software artifact(s) that can be run on a computer.
- 47. Testing which is performed on a software application by providing the valid data sets as an input.
- 48. Tracking product that allows bug tracking and agile project management.
- 49. A process where tracker issues are identified and prioritized.
- 50. Testing to find out whether the updates or changes had caused new defects in the existing functions.
Down
- 1. A document that covers the end-to-end functionality of the software very briefly, mostly in one line, from an end-user perspective.
- 2. Is a type of software testing that evaluates the overall functionality and performance of a complete and fully integrated software solution.
- 4. Testing activity that determines the robustness of software by testing beyond the limits of normal operation.
- 5. A way to check system performance for high data loads.
- 6. A type of performance testing in which an application receives a sudden and extreme increase or decrease in load.
- 10. A description of how a user interacts with a system or product.
- 12. Practice of testing how easy a application design is to use.
- 15. Testing where developer and tester work together
- 17. A detailed document that catalogs the test strategies, objectives, schedule, estimations, deadlines, and resources required to complete that project
- 19. A form of testing that is performed with no knowledge of a system's code.
- 20. Testing two or more integrated systems in order to ensure that the system works properly.
- 23. An informal, general explanation of a software feature written from the perspective of the end user or customer.
- 26. The specific set of states that defect or bug goes through in its entire life.
- 27. A type of non-functional testing which is done to check if the software system can sustain under a huge expected load continued over a long period of time.
- 30. A scale or full-size model of a design or device, used for teaching, demonstration, design evaluation, promotion, and other purposes.
- 31. Testing that uncovers vulnerabilities, threats, risks in a software application and prevents malicious attacks from intruders.
- 32. Performed without any planning and documentation. It is unstructured, unplanned, and informal testing.
- 33. A two-dimensional illustration of a page's interface that specifically focuses on space allocation and prioritization of content, functionalities available, and intended behaviors.
- 34. A process used to test software and ensure that quality standards are met.
- 37. A popular framework used to implement agile and DevOps software development.
- 38. A type of software testing that validates the software system against the functional requirements/specifications.
- 40. Prioritized list of work.
- 43. Testing performed to validate the build that hasn't changed for a period of time. Should be repeated for every new release.
- 46. A way of testing the smallest piece of code that can be logically isolated in a system.